The recordspec metadata CLI query is returning extra record specs

[SpicyLemon]

Summary of Bug

The provenanced query metadata recordspec <record spec id> CLI command is returning more record specifications than just the one requested.

Version

v1.19.1

Steps to Reproduce

1. Run the command provenanced query metadata recordspec recspec1qhe5jmlq8n9mm09el5dnuytz625j2vnjxcq5qn4t62ld7tu9djvq50cgcrv against a mainnet node.

Expected result:

The response has a record_specification field with just the recspec1qhe5jmlq8n9mm09el5dnuytz625j2vnjxcq5qn4t62ld7tu9djvq50cgcrv record specification in it.

Actual result:
The response has a record_specifications field with 15 record specifications in it, one if which is the one requested.

It appears that the CLI command is actually using the RecordSpecificationsForContractSpecification endpoint here instead of the RecordSpecification endpoint.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned