(client): lodestone availability testing

[ReidWeb]

Description

The client should have a mechanism to detect lodestone availability so that requests can be paused by consumers in the event of the site becoming unavailable

Use Case

As a consumer of the lodestone module I should be able to get a clear response indicating the lodestone is down, both as a consumable method .getStatus() and as a uniform response across all entities.

Proposed Solution

Incorporate into all entity fetch operations means to indicate the lodestone is down.

Develop a method routing to a page that should be available consistently and use the response from that to indicate status.

Other information

Curl responses

GET /worldstatus/

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change

[ReidWeb]

Testing of code in place to date verified as functional for Character entity, 2022-04-11 12:40:00Z.

Timeout had to be increased in client initialization, timeout errors were being presented

unsure if this is due to my current network connection or due to the server side.

Most likely the former, but verification needed.

[ReidWeb]

It appears HEAD requests respond with a 503 too. So LodestoneClient can have a getStatus() method that uses a HEAD request.

Verified via CI build test run that timeout increase was only needed on my local machine.