[uss_qualifier] Use FlightIntentsResource in general flight authorization scenario

[BenjaminPelletier]

Currently, the general flight authorization scenario defines FlightInfoTemplates (flight intent descriptions) directly in the FlightCheckTable. This is less than optimal because

• We have other tooling for loading flight intents (specifically: FlightIntentsResource)
• We may create more tooling to manage flight intents when in the standard form (a collection of FlightInfoTemplates)
• Always fully defining flight intents in the table disallows definition of delta flight intents as FlightIntentsResource allows

This PR generalizes and expands the general flight authorization scenario's treatment of flight intents by only specifying a flight intent ID in the table, and then using a separate standard FlightIntentsResource to provide the actual flight intents. The dev configuration and associated resources are updated.

Also, one additional field is added to the FlightCheckTable to reflect the new generalized flight planning interface: ExecutionStyle.

When this PR is merged, users of the general flight authorization scenario will need to update their configurations to move their flight intent definitions out of the table and into a separate FlightIntentsResource.

[barroco]

Would it make sense to reference the $schema here?

[BenjaminPelletier]

The $schema elements are really just human-readable comments, but makes sense to have them in the intents; added.