[openapi] move or add fields from injection.yaml to commons.yaml

[Shastick]

To prepare for some changes to the injection and observation API that is required for interuss/monitoring#754, this PR moves and adds some object definitions to commons.yaml, so they may be referenced from both injection.yaml and observation.yaml in subsequent PRs.

Definitions and behaviors should still be equivalent to before.

[mickmis]

In injection.yaml this is known as RIDAircraftType. Reason is that RIDAircraftType is taken from v19 and UAType is taken from v22a. The only practical difference seems that in v22a the value VTOL is not present anymore.
However now for the testing interfaces we want a single interface and not two different ones.

Here I'd be tempted to:

• remove RIDAircraftType from injection.yaml
• reference the common UAType here
• add here the VTOL value with a note

That should result in a compatible API. WDYT? Maybe another subject for the weekly today.

[Shastick]

Interestingly, while RIDAircraftType is defined in injection.yaml, it is not used anywhere in the actual API definition (meaning we can change it at will without breaking anything)

[Shastick]

As discussed at the weekly meeting, will add the VTOL enum to UAType, and only keep UAType for the injection.

It will be the USS's job to map this to the v19 version of things if they are implementing that version of the standard.

[Shastick]

@mickmis updated as discussed at the meeting (keep UAType, add VTOL to it, remove RIDAircraftType)

[mickmis]

I realized that there is one more difference for some fields between their v19 and v22a versions: their default values. Given that it is a (subtle) behavior change of an interface I think it's important to isolate that in a separate PR/commit with a version increment.

Example in this PR:

• old HorizontalAccuracy: v19, new: v22a
• old VerticalAccuracy: v19, new: v22a
• old and new SpeedAccuracy: v19

So I propose the following course of action:

• Update this PR that moves/add schemas so that there is no behavior change at all (i.e. keep the v19 versions, including RIDAircraftType as is)
• Add a new PR migrating schemas to v22a (including RIDAircraftType -> UAType with the VTOL exception), there do a version increment

[mickmis]

LGTM thanks