Add a checkbox to check-in group/type configuration that enforces a group's Group Requirements at the point of check-in, preventing a group member who does not currently meet those requirements from checking in to that group.

Current Behavior: Check-in configurations can already restrict check-in to existing group members. However, this "must already be a group member" setting does not take Group Requirements into account. A person can be a group member in good standing on paper, but out of compliance with a requirement (background check expired, required training not completed, document missing, etc.), and still be allowed to check in.

Group Requirements themselves can be configured to block someone from being added to a group in the first place, but they do not force removal or block check-in for someone who later falls out of compliance after being added.

The Problem This Creates: Because Group Requirements don't retroactively remove or restrict a non-compliant member, most churches configure requirements to allow adding people to the group anyway, and rely on the requirement status being visible in the group member list as a manual flag.

This creates two problems:

1. Group leaders must manually watch for red/non-compliant requirement flags and remember to keep a person out of service, with no system-enforced backstop.

2. Some churches instead try to maintain two parallel group structures, one for fully-qualified members and one for members who are still working through outstanding requirements, just so check-in can safely restrict to "group members only." This duplicate structure is confusing to maintain and easy for it to fall out of sync.

Proposed Solution: Add a checkbox option to the check-in configuration (at the Configuration level) such as "Enforce Group Requirements". When enabled, a person who is a member of the group but does not currently meet all of the group's requirements would not be presented as a valid check-in option for that group, the same way a non-member is excluded today.

This checkbox should default to unchecked, so existing check-in configurations continue to behave exactly as they do today unless an admin opts in.

Why This Matters: This lets churches use Group Requirements the way they're designed to be used, as a visible compliance flag rather than a hard add/remove gate, while still giving check-in a reliable, automatic way to keep non-compliant members from serving. It removes the need for workaround group structures and reduces reliance on manual monitoring by group leaders.