Fix Datalink inputs

[somebody1234]

Pull Request Description

• Fix Data Link modal: Missing fields of an optional entry wrongly highlighted red #11370
  • Disable validation for (and grey out) entries for children of disabled keys
• Fix Data Link modal: widget for selecting Secret path opens automatically when a datalink preview is opened #11372
  • Avoid opening Autocomplete dropdown automatically when autoFocus is not true
• Fix wrong default value being applied when editing a key that is currently absent

Important Notes

None

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• ~~If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.~~

[PabloBuchu]

1. If I type datalink name that already exists the modal is successfully submited but request ends with 400
2. Looks like for Postgres connectors all is now optional. I can create one with missing hostname, database name. Only port is required (similar to snowflake)
3. Can we make the red border around required attribute bit stronger? Is there enough space to also include something like "You need to provide URI" also we should change the validation text for name (will provide that with James)

[somebody1234]

If I type datalink name that already exists the modal is successfully submited but request ends with 400

i think this is out of scope unfortunately. the way the event handler currently works, we cannot await it to see if it succeeded. it's possible to fix but will require larger logic refactors

[radeusgd]

2. Looks like for Postgres connectors all is now optional. I can create one with missing hostname, database name. Only port is required (similar to snowflake)

+1 to that - it seems that I can create a data link without hostname or database name - but these 2 fields are required. Such datalink gets created but then when I .read it in Enso it of course fails to open as its invalid.

[radeusgd]

I think this may be too simple for the fix we need.

Fields that are themselves required, should still be marked red and not accepted if they are absent.

Only required sub-fields whose parent field is optional, do not have to be required.

[somebody1234]

i guess this is a bit of a misnomer - isAbsent means that the parent field is optional

[somebody1234]

Foo (object field, optional, currently absent, isAbsent = false)
  Bar (isAbsent = true, not optional)
  Baz (isAbsent = true, not optional)

[radeusgd]

i guess this is a bit of a misnomer - isAbsent means that the parent field is optional

Oh... Yeah so that name is a bit misleading indeed

[radeusgd]

Hmm, I see. It may be that the Postgres always allowed empty string for hostname/database name. So the fields are not actually missing, they are just "".

I guess we may want to change the schema to require at least host to be non-empty. Not sure if empty database string makes sense.