Collections search issues and improvements

[mcbouslog]

Largely duplicate of zooniverse/front-end-monorepo/issues/6235

Expected behavior

• I can search for and select a collection with a display name of 3 or less characters that is not one of my most recent 100 collections

Current behavior

• collection search requests a user's most recent 100 collections (regardless of display name) and filters the 100 recent collections by display name as the first 3 characters are typed in the search input
• after 3 characters collection search makes a request to panoptes to search for the collection
• if a collection is not in a user's most recent 100 collections and is 3 or less characters it will not be selectable from collections search

Steps to replicate

• related Talk discussion: https://www.zooniverse.org/talk/17/3411492
• related PFE PRs/issues: #7150 , #7124 , #7121
• related FEM PRs/issues: zooniverse/front-end-monorepo/pull/6127 , zooniverse/front-end-monorepo/issues/6120

Additional information

• related Slack thread noting Panoptes collections search code: https://zooniverse.slack.com/archives/C0DTP3L2K/p1723739207126769
  • collections_controller: https://github.com/zooniverse/panoptes/blob/master/app/controllers/api/v1/collections_controller.rb#L19-L21
  • index_search: https://github.com/zooniverse/panoptes/blob/master/app/controllers/concerns/index_search.rb

[mcbouslog]

As noted in the linked Talk discussion, collections with 3 or less characters that are not a user's most recent 100 collections appears to be an uncommon edge case. Since it's such an uncommon edge case, and the improvements in #7124 that close issue #7121 are much more common, I think this is issue is not urgent.

[mcbouslog]

Possible next steps:

• implement a 4 character minimum on collection display name creation
• refactor collections search without filtering as type and to search the API on input submit