[ADVISING-1003]: Enforce License Rules for Forms

[mxm1070]

Ticket(s) or GitHub Issue

https://engage.canyongbs.com/workgroups/group/3/tasks/task/view/1003/

Technical Description

Enforce License Rules for Forms.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• New feature (non-breaking change which adds functionality)

Screenshots (if appropriate)

Any deployment steps required?

A deployment step could be a command that needs to be executed or an ENV key that needs to be added, for example.

• No

---

Before contributing and submitting this PR, make sure you have:

• Read the contributing guidelines.
• Title the PR with the ticket/issue number and a short description of the changes made. Or if no ticket/issue exists, title the PR with a short description of the changes made
• Linked a relevant ticket or issue or describe the issue/feature which this PR resolves/implements.
• Resolved all conflicts, if any.
• Rebased your branch PR on top of the latest upstream develop branch.

[Orrison]

Looking great!

Let's do the same thing in Forms that we did for Applications. See EnsureOnlineAdmissionsFeatureIsActive and apply that to the forms API routes.

That way the widget does not render if the feature is off.