Add scope selection UI to pick list form

[bronwyncombs]

Problem

Currently, there are two issues with pick list scoping

1. if the entire table and field from table type pick lists are set as unscoped in collection preference, this only applies if the pick list is on the collection, discipline, division, or institution tables. see issue #7589, fixed by PR #8583.

2. if a pick list is created in collection A, the pick list and its items will also be available/used in collection B unless a conflicting set of pick list items is added. This is not the expected behavior. Schema config is scoped to the discipline, but we state that pick lists specifically are scoped to the collection in pick list documentation and in speciforum get help reply.
   However, it is appreciated by members, e.g., MCNB & CSIRO, because it means they don't have to duplicate the pick list and manage them separately across collections.

While problem 1. will be resolved soon, the solution to problem 2. could also improve the UX entire table and field from table pick list scope setting and functionality.

Solution

Add "scope to collection?" and "is global?" checkboxes to pick list form:

If scope to collection? is checked/true (default), the pick list will be scoped to the collection, which is the current expected behavior.

If unchecked/false:

1. a permission policy-like UI appears below with division > discipline name> collections > checkbox for each collection. It reflects the default scope, i.e., current collection so the checkbox for the current collection will be checked already
   And 2) a "Add Scope option also appears

If "Is Global" checkbox is true, the following policy will apply / appear:

"All Disciplines" Note - If the default policy for global scoping actually goes through an "All disciplines" option, the checkboxes here would have to be editable=false.
A better option is to just pass the default scope through Discipline. If one of the disciplines is unchecked from there, "Is Global?" will go back to false; editable=true

Expected Behavior for the Is Global and Scope to Collection checkboxes:

• If the "Is Global checkbox is true, the "Scope to Collection?" checkbox should be false; editable=false.
• If the "Scope to Collection?" checkbox is true, the "Is Global?" checkbox should be false; editable=false.
• If the "Scope to collection?" checkbox is false, the "Is Global?" checkbox should be editable=true.
• If the "Is Global" checkbox is false, the "Scope to Collection?" checkbox should be editable=true.

Cases to consider for entire table and field from table pick lists:

• what if the scope of table/field a pick list is set on is at or greater than collection or discipline
• what if the table or field from table is collection, discipline, division, or institution
• how to handle when a new field value or record is entered in one discipline (and thusly added as a pick list item) and that needs added/shared to other collections/disciplines included in the pick list's scope.
• what about tables and fields that have different uses and meanings across disciplines/divisions

Requested by:

CSIRO (speciforum post)
Ohio Inverts (speciforum post)
AAFC (speciforum comment)
MCNB (memebership email)