Error messages needed for ConfigurationStore save and load exceptions

[mnuttall-ibm]

Developer note

This is categorized as a release bug. The update is to add error messages to two code points which capture exceptions and which handle them with automatic FFDC. While new error messages are generated, these will only appear when FFDC is also generated. Other than adding the error messages, no code updates were made. No code which runs outside of error paths was changed.

Describe the use case that you want to enable:
The MQ Web Console Address Space may hang if the file system where MQ places its configuration files becomes full. This can fail in the form of an unexpected EOF encountered while reading a configuration file.

Describe why this is important to you:
The fact that the hang is caused by a file system shortage is difficult to diagnose. There needs to be a message issued when the failure happens to alert the user that a file system shortage needs to be relieved to correct the problem. A message such at the following would be appropriate:

XXXXXXE: Cached server configuration data could not be read from the file <LOCATION>.

An error occurred while attempting to read cached server configuration data.  That may
be caused by incomplete or corrupt cached data, or because of a problem accessing the target location.

The cached server configuration data should be cleared and re-saved by restarting
the server with the --clean option.

In relation to a z/OS zFS, if the problem occurred because no space was available on
the file system associated with the target location, consider setting the MOUNT
property AGGRGROW for that filesystem location.

Additional context
See Case TS020989149 for complete details.

[tbitonti]

There are two locations where IO to server configuration cache files catch exceptions, both in open-liberty/dev/com.ibm.ws.config/src/com/ibm/ws/config/admin/internal/ConfigurationStore.java.

One of the locations is writing the configuration cache. The other location is for reading the configuration cache.

I've put in new error in both locations.

See the changes to open-liberty/dev/com.ibm.ws.config/resources/com/ibm/ws/config/internal/resource/ConfigMessages.nlsprops for the final message text. Here is the pre-review text:

# {0} The location of the resource which could not be written.  This is a file used internally for caching the server configuration.
# {1} A message obtained from the exception which occurred when attempting the write.
error.config.cache.write.failure=CWWKG0111E: Server configuration data could not be written to the file [{0}].  Exception: {1}.  See the associated FFDC for additional exception details.
error.config.cache.write.failure.explanation=An error occurred while attempting to write server configuration data to an internal cache.  The target location may not be writable due to permissions problems, or because inadequate storage is available.  The failure may cause the internal cache to be corrupted, which may lead to error CWWKG0111E.
error.config.cache.write.failure.useraction=The server cache data should be cleared and re-written by restarting the server with the --clean option.  In relation to a z/OS zFS, if the problem occurred because no space was available in the file system associated with the target location, consider setting the MOUNT property AGGRGROW for that filesystem location.

# {0} The location of the resource which could not be read.  This is a file used internally for caching the server configuration.
# {1} A message obtained from the exception which occurred when attempting the read.
error.config.cache.read.failure=CWWKG0112E: Server configuration data could not be read from the file [{0}].  Exception: {1}.  See the fassociated FFDC for additional exception details.
error.config.cache.read.failure.explanation=An error occurred while attempting to read server configuration data from an internal cache.  That error may be caused by incomplete or corrupt cached data, or because of a problem accessing the target location.  The error may be caused by a prior failure to write the configuration data, which causes error message CWWKG0111E.
error.config.cache.read.failure.useraction=The server cache data should be cleared and re-written by restarting the server with the --clean option.  In relation to a z/OS zFS, if the problem occurred because no space was available in the file system associated with the target location, consider setting the MOUNT property AGGRGROW for that filesystem location.

[tbitonti]

Fixed by #34033