[Autocomplete] support reset on focus

[zairigimad]

Q	A
Bug fix?	yes
New feature?	no
Deprecations?	no
Documentation?	no
Issues	Fix #3415
License	MIT

It’s not actually a bug, but the default behavior of Tom Select.
When the preload option is set to focus (which is the default), it fetches the data once and then reuses the cache to avoid triggering a request every time the select is opened.

With this PR, a new option is introduced to let you control whether the state should be reset on focus or not.

[github-actions]

📊 Packages dist files size difference

Thanks for the PR! Here is the difference in size of the packages dist files between the base branch and the PR.
Please review the changes and make sure they are expected.

File	Before (Size / Gzip)	After (Size / Gzip)
Autocomplete
controller.d.ts	1.83 kB / 655 B	1.91 kB+4% 📈 / 667 B+2% 📈
controller.js	12.93 kB / 3.45 kB	13.3 kB+3% 📈 / 3.54 kB+3% 📈

[brianfreytag]

Thanks for the clarification on the default functionality and I agree that an additional option here is the best solution.

I do want to clarify that it's not just on "focus" or "change" events, it's when the reset X is pressed as well to clear the input. Would it not make sense that the default functionality of "clear" would be to actually reset the select options than maintain the cached version? I guess in my mind, if I'm clearing the input, I'm trying to go back to the original state whether I begin a new search or decide I want to scroll this time.

This question to ask, I suppose, is, "Should the default value for reset_on_focus be true in instances of the "clear" button?" and is this something to take up with the TomSelect folks or a "workaround" on the Symfony side?

[Kocal]

Since it's not really a bug but a feature, can you add a new changelog entry for 2.35 please?

Thanks!

[Kocal]

Please remove the as any, it's often a bad practice, and it does not make sense here AFAIK.