Capabilities API labeled deprecated but Capability Controllers aren't yet on m

[sisyphusSmiling]

Problem

The Capabilities API is planned to be deprecated in favor of Capability Controllers (CapCons), but CapCons are not yet live on Mainnet and VS Code extension notifies devs that the existing Capability API is deprecated.

A dev following the instructions presented would find a lack of documentation on the suggested API and be frustrated to find out that the API they implemented isn't yet supported on Mainnet.

Steps to Reproduce

1. Run emulator
2. Attempt to retrieve a Capability using the existing API

Acceptance Criteria

The notice is removed until CapCons are live on Mainnet at which point the plan is to support a transition period between APIs and the deprecation notice would be appropriate.

Context

Originally thought CapCons were a blocker for Mainnet deployment, but realized the feature is not yet supported.

[m-Peter]

I will have a shot at this 🙏

[m-Peter]

There are some more functions that have the same issue, that is described above. E.g:

[m-Peter]

Opened a PR to address this: onflow/cadence#2673