Describe the bug

see https://www.loom.com/share/8fc3f55bc2594c30a806cc7cb8dc4c71
there are also other instabilities in the field, but harder to pinpoint. maybe by solving this one we also fix the others?

Side question, is there a way to use the belongs_to + searchable: true field (see screenshot) in MULTIPLE mode? That search works flawlessly

Reproduction repository for the bug

          field :leader_ds,
                as: :tags,
                suggestions_max_items: 999,
                enforce_suggestions: true,
                fetch_values_from: -> do
                  Avo::Engine.routes.url_helpers.leader_planning_suggestions_path
                end,
                suggestions: ::Leaders::PlanningSuggestions.new(record, current_user).suggestions,
                format_using: -> { [] }

Steps to use in the reproduction repository

Steps to reproduce the behavior:

1. Add this configuration '...'
2. Go to '...'
3. Click on '....'
4. Scroll down to '....'
5. See error

Expected behavior & Actual behavior

System configuration

Avo version: 3.21.1

Rails version: 7.2.1

Ruby version: 3.2.2

License type:

• Community
• Pro
• Advanced

Are you using Avo monkey patches, overriding views or view components?

• Yes. If so, please post code samples.
• No

Screenshots or screen recordings

Additional context

Impact

• High impact (It makes my app un-usable.)
• Medium impact (I'm annoyed, but I'll live.)
• Low impact (It's really a tiny thing that I could live with.)

Urgency

• High urgency (I can't continue development without it.)
• Medium urgency (I found a workaround, but I'd love to have it fixed.)
• Low urgency (It can wait. I just wanted you to know about it.)