Dependencies: frame-metadata features change

[OverOrion]

Since paritytech/frame-metadata#62 new features flags are used instead of the old / current ones (v14 -> current after a quick glimpse).

This means that for some PRs where our dependencies are updated a sudden build failure is expected.

I believe this affects the substrate-api-client as well, so tagging @haerdib.

[clangenb]

In the current state, if someone wants to use the integritee-cli as a lib, and hasn't generated a Cargo.lock file yet, the build is broken because cargo can't handle if features are not available on the latest commit of a branch. This patch resolves the issue until it is solved for good:

[patch."https://github.com/paritytech/frame-metadata.git"]
frame-metadata = { version = "=15.1.0" }