Program designation restriction: Suspension

As a ministry user I need the functional tools to be able to handle institutions according to policy without needing to have lasting impact on the institution.

This epic will focus on Suspension Restriction

### Use case
PTIB suspends a program but not a Location or an Institution. In this case Ministry does not want to allow any new offerings. No new applications will be allowed. Already existing applications will require Ministry review. If money were disbursed, no action.

### Create Suspension restriction that can be applied by a ministry user to a program:

- The restriction is applied at the program level. Can be also applied across all locations at once.
- No new public or private offerings are permitted for the restricted program.
- Existing applications already in the system are blocked, preventing students from accepting their Notice of Assessment or receiving funding—unless Service Delivery manually removes the hold.
- New applications can be submitted, but the system will display the warning Banner
- The institution is aware that the program is suspended
- When restriction resolved, the blocked applications are automatically released.

### Bypass restriction
- Allow Ministry to bypass SUS
- If SUS is bypassed, it should have no impact on student app

Additional considerations:
Suspension vs. Train Out - Program Restriction
From a system perspective, Program Suspension and Train Out appear functionally identical, with the following outcomes when a restriction is applied:
We recognize that the business rules behind Suspension and Train Out may differ, particularly regarding the funding decision process. Staff may need to distinguish between these two scenarios. To support this, we can create two separate restriction codes, making it clear why a program has been restricted.

Worksheet that was reviewed by IPDT