Trigger options really aren't, mostly

We recently added spin up --key-value and will soon add spin up --sqlite. Because these have to be processed by host components, and because host components are loaded in the trigger process, these have to be declared on the trigger command, rather than directly on up. This means they appear in the TRIGGER OPTIONS part of spin up --help.

And yet they are clearly not, conceptually, trigger options. --listen is a trigger option. --tls-cert is a trigger option. But nobody trying to remember if it's --keyvalue or --key-value is going to look in the TRIGGER OPTIONS section. It's an implementation artifact.

It would be great to find a sustainable, maintainable way to present command options that are not specifically trigger-related in the main section of spin up --help, and have only truly trigger-related ones in the subsection.

Start by locating the spin up --help implementation and the definitions for --key-value, --sqlite, --listen, and --tls-cert. Determine how options are assigned to the main and TRIGGER OPTIONS sections, then define a maintainable presentation that keeps only truly trigger-related options in the subsection and verify the resulting help output.