Fix phantom schemas, wrong error codes, and copy-paste bugs in feature files (#53)

[DLondonoD]

What type of PR is this?

tests

What this PR does / why we need it:

Fixes multiple test bugs in Test_definitions/*.feature files where Gherkin
steps reference schemas, parameters, operations, or error codes that don't
match the OpenAPI spec:

1. Phantom schema references — createAppInstance.feature,
   createAppDeployment.feature, and updateAppDeployment.feature
   referenced nonexistent components (AppInstanceManifest,
   AppDeploymentManifest); the actual request bodies are anonymous inline
   object schemas. Replaced with generic "request body schema for this
   operation" phrasing.
2. Query parameters mislabeled as path parameters — appId,
   appInstanceId, region (getAppInstance.feature), appId,
   appDeploymentId (getAppDeployments.feature), and region, status
   (getEdgeCloudZones.feature) are all in: query in the spec but were
   described as "path parameter". Also fixed a copy-pasted region
   scenario that said "a valid application ID" instead of "a valid region".
3. Non-existent operation names — removeAppInstance/
   removeAppDeployment (don't exist) corrected to
   deleteAppInstance/deleteAppDeployment.
4. Invalid 410 scenario removed from getAppInstance.feature —
   GET /appinstances doesn't document 410 at all; the scenario was
   copied from the deployments feature file and never adapted (wrong
   entity id, nonexistent operation, leftover comment from the other file).
5. Invalid query filter — getAppDeployments.feature filtered by
   appInstanceId, which isn't a valid query parameter for
   GET /deployments (only appId/appDeploymentId are); replaced with
   a proper appDeploymentId filter scenario, and fixed several
   createAppInstance-labeled steps that should have said
   createAppDeployment.
6. Deprecated/wrong error codes — CONFLICT (deprecated per the
   Design Guide) asserted in submitApp, createAppInstance, and
   createAppDeployment's 409 scenarios; corrected to ALREADY_EXISTS,
   matching the spec's own examples. deleteApp.feature corrected to
   ABORTED, also matching its spec example.
7. Miscellaneous typos: appPorvider→appProvider,
   componentSpect→componentSpec, non-standard step phrasing in
   submitApp.feature; PascalCase KubernetesClusterRef corrected to the
   spec's actual kubernetesClusterRef/kubernetesClusterRefs; singular
   /deployment/{appDeploymentId} path corrected to plural
   /deployments/{appDeploymentId}; appDeploymentIdd typo; wrong
   AppInstanceInfo schema in updateAppDeployment.feature corrected to
   AppDeploymentInfo; list-response scenarios in getAppInstance.feature
   and getAppDeployments.feature corrected to assert against an array of
   the schema instead of a bare object.

Out of scope / left untouched: the wrong singular getEdgeCloudZone
operationId, the "When When the request..." typo, and the wrong
deleteApp/createApp operationIds referenced in
updateAppDeployment.feature, deleteAppDeployment.feature, and
createAppInstance.feature — these are already covered by issue #52's fix
in a separate branch/PR.

Which issue(s) this PR fixes:

Fixes #53

Special notes for reviewers:

This PR has two merge-order dependencies on other open PRs. Both were
verified with an actual local merge simulation (not just static analysis),
and real Git conflicts were confirmed in both cases:

1. PR #56 (fixes #48) removes 410 from getAppDeployments,
deleteAppDeployment, and updateAppDeployment (replacing it with 404
on the GET, and simply dropping it where 404 already existed on the
other two). This PR intentionally left the three corresponding
@eam_*_410.1_gone scenarios untouched, since as of this branch's base the
spec still documents 410 for those operations. Once #56 merges, those
three scenarios will test an error code that no longer exists there and
should be removed or converted to 404 as follow-up.

2. PR #58 (fixes #49) repurposes getAppInstance.feature from the
list operation (GET /appinstances) to a new by-id operation
(GET /app-instances/{appInstanceId}), moving the list scenarios into a
new getAppInstances.feature file, and removes getAppDeployments'
appDeploymentId query filter entirely (since it becomes redundant with
a new getAppDeployment by-id endpoint). This directly conflicts with
this PR's changes:
- getAppInstance.feature: this PR fixes it as the list operation
(query-param labels, array-schema assertion, removed invalid 410
scenario); after #58, that content semantically belongs in
getAppInstances.feature instead, and getAppInstance.feature will
mean something entirely different (by-id).
- getAppDeployments.feature: this PR adds a "filtered by
appDeploymentId" scenario (replacing the invalid appInstanceId
one); #58 removes that same filter as redundant with its new
by-id endpoint — the two changes are directly opposed.

Recommendation: merge #58 (and ideally #56) first, then rebase/redo
this PR's getAppInstance.feature and getAppDeployments.feature fixes
against the post-#58 file layout (i.e., apply the equivalent fixes to
getAppInstances.feature instead of getAppInstance.feature, and drop the
now-redundant appDeploymentId filter addition). The other 7 files touched
by this PR (submitApp, deleteApp, createAppInstance,
createAppDeployment, deleteAppDeployment, updateAppDeployment,
getEdgeCloudZones) are unaffected by either #56 or #58 and can land
independently.

Changelog input

release-note

Additional documentation

This section can be blank.

docs