chore: retains apiversion in app description and app deployments

[vireshnavalli]

Description

As the API routes include version within URL there is not need to explicitly have 'apiVersion' attribute for margo specified REST apis . Keeping the apiVersion in ApplicationDescription and ApplicationDeployment, although the version string needs to be the same as the OpenAPI version and follow semantic versioning.

Issues Addressed

Address #134

Change Type

Please select the relevant options:

• Fix (change that resolves an issue)
• New enhancement (change that adds specification content)
• Content edits (change that edits existing content)

Checklist

• I have read the CONTRIBUTING document.
• My changes adhere to the established patterns, and best practices.

[nilanjan-samajdar]

The apiVersion should be v1.0.0-rc.2
Corresponding to the recently release spec version v1.0.0-rc.2

[phil-abb]

Issue #134 is in the Gen. Improvements SUP Required column. There was no SUP for this creation.

[jachstet-sea]

Since apiVersion: margo.org/v1-alpha1 is what is contained in the tags https://github.com/margo/specification/releases/tag/v1.0.0-rc.2 and https://github.com/margo/specification/releases/tag/plugfest-2026-07 I assume that the change proposed here (which makes sense) will be done AFTER the July Plugfest and we will keep apiVersion: margo.org/v1-alpha1 for the plugfest?

[ajcraig]

Issue #134 is in the Gen. Improvements SUP Required column. There was no SUP for this creation.

Yes, @vireshnavalli please close this PR and recreate as a SUP within the specification enhancements repository.

Since apiVersion: margo.org/v1-alpha1 is what is contained in the tags https://github.com/margo/specification/releases/tag/v1.0.0-rc.2 and https://github.com/margo/specification/releases/tag/plugfest-2026-07 I assume that the change proposed here (which makes sense) will be done AFTER the July Plugfest and we will keep apiVersion: margo.org/v1-alpha1 for the plugfest?

@jachstet-sea: This PR will be closed so changs will not be implemented prior to plugfest. As for the API definition that will be the baseline for Plugfest testing, the current version is 1.0.0 although incorrect that's what we will run with during plugfest.

I'll let the newly created SUP work out the API versioning strategy.

[linux-foundation-easycla]

[vireshnavalli]

@margo/technical-wg / @margo/development-team changes for #189 is ready for review.

[vireshnavalli]

Hi @matlec @ajcraig Could you please review this once.