Team Plan cont. (disabling project coverage centric yaml configs)

[rohan-at-sentry]

Problem to Solve: Currently a Team plan org can configure and utilize any yaml configs currently available in Codecov with no restrictions despite the Team plan not actually displaying project coverage or coverage over time.

Proposed Solution: Add some sort of blocking to project coverage centric yaml configs, this includes basically anything to do with:

• Project coverage
• Components
• Flags
• Carryforward flags

This MUST also include a notification to the end user that they're not able to access the feature due to their plan with potentially an upgrade prompt where reasonable.

[aj-codecov]

Added this issue to #912 for tracking on the master epic