Add VM Metrics

[brew0722]

No description provided.

[brew0722]

There is already a metric record that can replace compilation time and execution time after 0.14.0-alpha1.
CosmWasm/wasmd#463
It makes sense enough as I'm recording execution times for Instantiate and Execute. Of course, the other runs are also included in the metrics, but that seems good enough for the JIT bomb or gas consumption measurements we're concerned about.

The telemetry metrics is included :1317(API Server metrics).
{"Name":"wasm.contract.instantiate","Count":1,"Rate":2.222800064086914,"Sum":22.22800064086914,"Min":22.22800064086914,"Max":22.22800064086914,"Mean":22.22800064086914,"Stddev":0,"Labels":{}}]}

And VM cache metrics is included :26660(Instrumentation via tendermint).

# HELP wasmvm_cache_elements_total Total number of elements in the cache
# TYPE wasmvm_cache_elements_total gauge
wasmvm_cache_elements_total{type="memory"} 1
wasmvm_cache_elements_total{type="pinned"} 0
# HELP wasmvm_cache_hits_total Total number of cache hits
# TYPE wasmvm_cache_hits_total counter
wasmvm_cache_hits_total{type="fs"} 1
wasmvm_cache_hits_total{type="memory"} 0
wasmvm_cache_hits_total{type="pinned"} 0
# HELP wasmvm_cache_misses_total Total number of cache misses
# TYPE wasmvm_cache_misses_total counter
wasmvm_cache_misses_total 0
# HELP wasmvm_cache_size_bytes Total number of elements in the cache
# TYPE wasmvm_cache_size_bytes gauge
wasmvm_cache_size_bytes{type="memory"} 3.036677e+06
wasmvm_cache_size_bytes{type="pinned"} 0