feat: Enable cli flags

[yejseo01]

Changes

• Added target deploy settings UI via the target view gear button.
• Added settings:
  • topo.defaultTargetDeploySettings
  • topo.targetDeploySettings
• Added deploy flag support:
  • port -> -p
  • forceRecreate -> --force-recreate
  • noRecreate -> --no-recreate
• Added validation for ports, unknown keys, and conflicting recreate flags.
• Preserves malformed JSON settings when opening settings, but ignores them during deploy.
• Seeds cached targets and missing default fields into settings JSON.
• Added tests for deploy flags, defaults, target overrides, validation, and settings seeding.

Screenshots

Confirmed with @ZachMaso on the UI.

[awphi]

I'm open to other opinions here but I strongly dislike pressing a button in the tree view writing a bunch of stuff to my config. ensureCachedTargetDeploySettings is probably the worse offender since it can write a lot potentially.

[yejseo01]

I can think of one way, where we just leave it empty when the target doesn't have any custom deploy settings. However, I feel like that makes it more confusing for the users to add custom settings. When they start topo for the first time, they won't have any example json object that resembles the deploy options. Can you think of any other way?

[yejseo01]

Along with above, we can also make a command palette+quick pick path to add a custom deploy options. It would be shown/editable by the settings page, but if we have another way to edit the deploy settings(command palette + quick pick), it would be a good way to guide the user even when there are no example deploy option object in the settings?

[awphi]

Behavioural question I don't have strong opinions about - should we throwing away all the config if one value is invalid. i.e. if set noRecreate: "foo" we'll discard my custom port atm

[yejseo01]

what do you mean by "discard"? are we not deploying at all or deploying with no flags? I think it should either be not deployed or deployed with flags. I don't think we should deploy with no flags for flags being invalid. that is weird

[awphi]

Should we be constraining this to deploy? We've talked in the past about other target-specific config we want to set and it would feel nasty imo to have something like

{
  "topo.targetDeploySettings": {
     "target": {
        "port": "12345"
     }
  },
  "topo.extensionSettings": {
     "target": {
        "refreshInterval": 3000
     }
  }
}

perhaps would be neater to generify this and scope deploy settings like:

{
  "topo.targetSettings": {
     "target": {
         "deploy": {
            "port": "12345",
         },
         "refreshInterval": 3000 // added later if ever ofc
     }
  }
}

[yejseo01]

I think it is okay to constrict this to deploy. it is already in the deploy section within the topo settings. any other target agnostic settings should be outside the annoying json format in my opinion

[awphi]

This is currently an uncaught error as it stands which I'm not sure if what we want for a validation error?

[yejseo01]

I'm not sure what you mean? can you rephrase the sentence?