Add guardrails to CP workflow for validationg legal agreement for a spec project

Description

For specification projects, the current process to validate legal agreements is still manual and error-prone. Foundation staff must review agreements in FoundationDB and check a box confirming: “I have verified the paperwork of this specification project.” This allows the CP to move forward even if required agreements are missing.

Important Detail

A specification project is always affiliated with a Working Group.

Example: A Specification Project affiliated with the Jakarta EE Working Group must validate agreements tied to that WG.

• If the elected committer works for a member company, the required agreement is a MCCA and the WPGA for that Working Group.
• If the elected committer does NOT work for a member company, the required agreement is Committer Member + the IWGPA for that Working Group.

The list of agreements for a WG can be retrieved via the Working Group API:

• Example: https://api.eclipse.org/working-groups/jakarta-ee/agreements
• Docs: https://webdev.eclipse.org/docs/api/eclipsefdn-working-groups-api/#/paths/~1%7Balias%7D~1agreements/get

Proposal

Add guardrails to the CP workflow (spec projects only) so that:

• The system verifies the presence of the correct WPGA or IWGPA for the project’s affiliated WG.
• If the required agreement is missing, the reviewer is blocked from moving the CP forward.

Goal

Validate manual steps to ensure specification projects cannot proceed without the proper Working Group–specific legal agreements in place.

/cc @wbeaton @scorbett @javiervalino @skilpatrick @mdelgado624