Block release not using the release planner app

### Problem:
All of our release docs and process are now run through the Release Planner App and any updates to the process are reflected in the information in the app or the docs it points to. But some partner teams are still "running rouge" and releasing not using the Release Planner App. This means they do not see the updates to our release process and continue to use the old process which in some cases no longer works properly.
Not following our new processes often leads to incomplete releases, like not having the proper metadata along with their release to have it properly show on the Releases Site or in Ref Docs ToCs.

### Possible Solution
Add additional checks that grantee releases have an accompanying release plan.
I try and do this already by forcing teams that come to the Arch Board to link a release plan, but that only stops or delays their Arch Board meeting. If they are not even planning to come to the Arch Board, they will get around this.

Adding a check for a release plan in the release pipeline could help stop teams from releasing who haven't completed all the needed steps.

### Considerations
There may have to be a way for our own SDK teams to get an exception as some have not adopted the release planner fully yet and their scenarios may not be covered.

To help resolve some scenarios where this check would not be wanted, maybe it should follow the same requirements for when an Arch Board meeting is needed. (On first beta releases and stable releases)