Handle scoping for Picklists based on Field in Table

[melton-jason]

Fixes #4989

The Issue here was that for Picklists based on field values for a table, the frontend was always trying to enforce scoping for for records of the table the "fictitious" Picklist Items were based off of.

See #4989 (comment)
Related: #3564

Checklist

• Self-review the PR after opening it to make sure the changes look good
  and self-explanatory (or properly documented)
• Add automated tests
• Add relevant issue to release milestone

Testing instructions

• Create a PickList with type "Field From Table"
• Choose a Table which can not be scoped
  • Some examples include:
    • AccessionAuthorization
    • Author
    • CollectionRelationship
    • CollectionRelType
    • Disposal
    • SpecifyUser
    • SpQuery
    • TaxonTreeDefItem
• Choose any field from the Table
• In any field on any table (can be different from the table chosen above) in the Schema Configuration, assign the PickList to the field
  • Related Speciforum Docs
• Navigate to any form of the table which contains the field assigned to the PickList and ensure no error is thrown

---

• Navigate to any existing CollectionRelationship form
  • Some Test Panel databases which contain CollectionRelationships:
    • mpabi_2024_06_04
    • KUFish_5_16_23
    • SAIAB_11_24_23
• Ensure an error does not occur and the CollectionRelType is properly populated

[maxpatiiuk]

I think it's the back-end's job to figure out if a table can be scoped and if so scope it.
Front-end saying "domainFilter: true" should be interpreted as "scope these resources if you can, please"

[grantfitzsimmons]

@CarolineDenis This was reported again today by MCNB, can we add this to our timeline? It looks like the work is (largely) done on it already