Connectionpool Metrics do not repopulate when restarting an application for all MP Metric features (that support monitor metrics)

[Channyboy]

Describe the bug
Connection pool Metrics do not repopulate when restarting an application for all MP Metric features (that support monitor metrics).

The metrics are removed when the application stops.

Steps to Reproduce

1. Deploy an application that makes use of a datasource (or datasource). During runtime of the application when a connection is created then the connection pool related metrics are created as well.
2. Stop the application (either removal, or update of the application)
3. Start the application and continue with runtime/business-logic.
4. No connection pool metrics.

Expected behavior
The connection pool metrics are created based on the connection pool MBean managed by the monitor-1.0 feature. According to the API, these MBeans are created for each data source that is configured (per server/jvm). Therefore, when an application is unloaded, the datasource is still present (i.e., configured via <datasource> in the server.xml + enablement with the jdbc feature). The expected behavior is to maintain the connection pool metric until the removal of the datasource (and not through the unloading of an application).

Diagnostic information:

• OpenLiberty Version: N/A
• Affected feature(s) mpMetrics-x.x
• Java Version: N/A
• server.xml configuration (WITHOUT sensitive information like passwords)
• If it would be useful, upload the messages.log file found in $WLP_OUTPUT_DIR/messages.log

Additional context
Add any other context about the problem here.