Add jvm memory and thread metric

[wzy531a]

jvm memory metric in runtime-metric only collect memoryPool, refer to splunk otel agent jvm memory metric:
p.r.jvm.memory.init
p.r.jvm.memory.max
p.r.jvm.memory.used
p.r.jvm.memory.committed

thread:
p.r.jvm.threads.live(Already exists)
p.r.jvm.threads.daemon
p.r.jvm.threads.peak
p.r.jvm.threads.states

About memory metric, I support Add JVM implementation information and memory semantic conventions, use p.r.j.memory.pool.* and p.r.j.memory.* to distinguish.

[mateuszrzeszutek]

Hey @wzy531a ,
With regards to memory metrics: MemoryPools and BufferPools offer pretty much the same information as Splunk's memory metrics (except the first two, these are a part of the memory profiling feature).
About the thread metrics: #6635 implements the daemon thread counter; the other two metrics are still not defined though.

[wzy531a]

Hey @wzy531a , With regards to memory metrics: MemoryPools and BufferPools offer pretty much the same information as Splunk's memory metrics (except the first two, these are a part of the memory profiling feature). About the thread metrics: #6635 implements the daemon thread counter; the other two metrics are still not defined though.

Both Splunk and Skywalking provide detailed metrics for memory and threads. So I think these metrics are necessary for memory and thread analysis.