Add MachineLearningServices stable API version 2026-07-01 (#44321)

* feat(machinelearningservices): add 2026-07-01 API version

Add the stable 2026-07-01 TypeSpec version and generated OpenAPI. Carry forward all preview-only feature gates, including the two AssetJobOutput fields restored after the original PR was opened, and correct embedded API versions in pagination examples.

Authored-by: GitHub Copilot CLI 1.0.78-3
Model: GPT-5.6 Sol (gpt-5.6-sol)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 64896f62-baee-4160-88ac-a3fa5e0ed2c7

* Scope PathForResourceAction suppression and fix readme heading spacing

Address ARM API review (findings 1 and 6) on the 2026-07-01 GA tag:
- Scope the blanket PathForResourceAction suppression to the single
  offending path (RegistryDataReferences_GetBlobReferenceSAS POST on
  registries/{registryName}/datareferences/{name}/versions/{version}),
  which is the only POST that violates the rule.
- Insert the missing blank line before the
  package-preview-2026-05-15-preview tag heading.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Scope 10 blanket LintDiff suppressions to exact paths (ARM review finding #3)

Convert the following blanket suppressions in the GA package-2026-07-01 tag
to exact per-path where: lists, so each suppression covers only its current
violations instead of the whole rule: ResourceNameRestriction, PostResponseCodes,
ProvisioningStateSpecifiedForLROPut, PatchBodyParametersSchema, PatchIdentityProperty,
PutResponseCodes, GetCollectionOnlyHasValueAndNextLink, XmsPageableForListCalls,
CollectionObjectPropertiesNaming, PatchResponseCodes.

Paths were derived by running the azure-validator (openapi-validator) over the
2026-07-01 spec with suppressions removed, capturing every violation per rule,
and formatting each to the exact jsonpath (validated against known-good
suppressions in this readme and repo-wide response-code conventions). Verified
locally: with these scoped where: lists all 10 rules report 0 violations, i.e.
the scoping is exactly as effective as the prior blanket suppressions.

ProvisioningStateMustBeReadOnly (finding #2) is intentionally left blanket
pending owner decision.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix PathForResourceAction suppression scope to path level (no .post)

The PathForResourceAction rule reports its violation at the path key
(jsonpath ["paths", "<path>"]) rather than at the .post operation, because
the rule's given navigates to the parent key (.post^~). The previous where:
entry targeted "<path>".post, which did not exact-match the violation, so the
suppression missed and LintDiff reported 1 new error. Drop the trailing .post
so the where: matches the path-level jsonpath (same pattern as the working
ResourceNameRestriction suppression). Verified locally: PathForResourceAction
now reports 0 violations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Add @secret to credential-bearing properties (SEC-SECRET-DETECT)

Annotate 8 credential properties with @secret so emitted swaggers carry
x-ms-secret: true (and format: password): VirtualMachineSshCredentials.password,
DatabricksProperties.databricksAccessToken, DatabricksComputeSecretsProperties.databricksAccessToken,
WorkspaceConnectionAccessKey.secretAccessKey, WorkspaceConnectionAccountKey.key,
WorkspaceConnectionApiKey.key, CustomKeys.keys, WorkspaceConnectionPersonalAccessToken.pat,
WorkspaceConnectionSharedAccessSignature.sas.

These values are redacted on GET/LIST/PUT/PATCH in the backend and returned
only via listsecrets/listkeys; the annotation closes the metadata gap. @secret
is not version-gatable, so x-ms-secret regenerates across all emitted versions
(additive, non-breaking).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* ci: re-trigger swagger validation on current head

Validation Analyze-Code runs were dropped in the GitHub Actions runner backlog when ce274e54b0 was pushed, leaving LintDiff/BreakingChange/ModelValidation/SemanticValidation/Avocado/Cross-Version as required 'Expected' statuses. Empty commit re-fires the pull_request synchronize event to republish them.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* fix(machinelearningservices): regenerate service metadata

Include the 2026-07-01 stable API version emitted by TypeSpec compilation.

Authored-by: GitHub Copilot CLI 1.0.79

Model: GPT-5.6 Sol (gpt-5.6-sol)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: c0a866e5-2354-4fdf-a20f-9f676aaab99d

* style(machinelearningservices): apply TypeSpec formatting

Apply the formatter output required by TypeSpec validation.

Authored-by: GitHub Copilot CLI 1.0.79

Model: GPT-5.6 Sol (gpt-5.6-sol)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: c0a866e5-2354-4fdf-a20f-9f676aaab99d

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 64896f62-baee-4160-88ac-a3fa5e0ed2c7
Copilot-Session: c0a866e5-2354-4fdf-a20f-9f676aaab99d