Autocomplete hook token/ID/URL fields from existing config

[caco3]

Adds autocomplete for hook credential fields (bot tokens, chat IDs, webhook URLs, etc.) based on values already present in the saved config. When a user focuses a supported hook field, a dropdown appears with existing values from other hooks identical to the ones for the paths. The dropdown also includes values from other hooks in the same form that have not yet been saved, making it easier to configure multiple similar hooks in one session.

This PR is an approach to solve the following issues:

• Reusable Hook Destinations #789
• Support global hooks #595

Notes

• This PR is AI driven. My Go skills are very limited. But I reviewed it and tested it.
• The implementation avoids the project's combobox component for hook fields because its state machine conflicts with the parent form's per-keystroke re-renders, which caused focus loss. Instead, a plain controlled input with a simple absolutely-positioned suggestion list is used.

[garethgeorge]

Hi, thanks for the interest in contributing!

Afraid for this one I'm concerned about the maintenance cost of serverside autocomplete for these fields. I think a client side only solution would be more interesting-- but I'm also wondering if this is broadly the wrong way of approaching the problem.

I think I'd like to tackle this more comprehensively at some point with a template / inheritance system allowing users to either copy and inherit configuration from other plans-- but some real thinking about the semantics of this are needed.

[caco3]

Thanks for the feedback!

I am not sure what you mean with " template / inheritance system". Could you elaborate a bit more, then I can give it a try.

As for the client side focus, how would you want to do this? At least once we would have to read the config file to extract the current values.

[caco3]

@garethgeorge ping :)