feat: get runtime metadata from WASM file

Why do we need this feature?

We learnt that this feature is used across commands like pop bench and pop try-runtime and it does increase the experience significantly.

• With pop bench, current issue is with the hooks and pallet names.
• With pop try-runtime, we can use this feature to compare the spec version / name of a remote node and a provided blob and throws the error early.

Current Status

Latest branch of https://github.com/chevdor/subwasm works well but the published version on crates.io is not up-to-date which makes the remote crate not compatible with our codebase. Need to consider alternative approach or re-implement our own version of the functionalities of subwasm that we need.