Expose a more complete set of information from the JMX export of InternalResourceGroup

[xkrogen]

Description

Add missing information from InternalResourceGroup to the set of metrics exposed when jmxExport = true to provide a more complete picture of the state of each resource group.

Additional context and related issues

Resource groups allow us to enable monitoring by using jmxExport = true (recently enabled by default in #20810, though subsequent reverted in #22185). However currently the set of information exposed by the resource group is restricted to a set of fields that seems fairly arbitrary to me, limiting the value. I would break the information into two categories: config information (e.g. what are the configured limits) and runtime information (e.g. how many queries are currently running). For this to be really useful, you need both things, so you can compare the current behavior against the limits, and you need a complete view of the picture. Below I list all of the fields from both categories, and the current status:

Type	Field	Currently Exposed?
Config	SoftConcurrencyLimit	NO
Config	HardConcurrencyLimit	YES
Config	SoftMemoryLimitBytes	NO
Config	SoftCpuLimitMillis	NO
Config	HardCpuLimitMillis	NO
Config	CpuQuotaGenerationMillisPerSecond	NO
Config	MaxQueuedQueries	YES
Config	SchedulingWeight	NO
Config	SchedulingPolicy	NO
Runtime	RunningQueries	YES
Runtime	QueuedQueries	YES
Runtime	WaitingQueuedQueries	YES
Runtime	CpuUsageMillis	NO
Runtime	MemoryUsageBytes	NO
Runtime	TimeBetweenStartsSec	YES

This PR exposes all of the fields that are marked with NO above, to consistently expose everything.

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(X) Release notes are required, with the following suggested text:

# General
* Expose additional JMX metrics about resource groups including cpu and memory usage, limits and scheduling policy in use. ({issue}`22957`)

[xkrogen]

cc @phd3 @hashhar @wendigo

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[xkrogen]

Thanks for the review @hashhar !