[Task] Legacy /bundle/* endpoints: OpenAPI hardening + consolidation into v1 publishing

Context

Surfaced by the Publishing Queue migration spike (#36039).

com.dotcms.rest.BundleResource (/bundle/*) is the legacy bundle REST surface. The new Angular portlet (#36040) consumes a mix of v1 (/v1/publishing/*, /v1/bundles/*) and these legacy endpoints. Several of the legacy endpoints have known quality issues that should be retired into the v1 surface:

Also surfaced by the audit:

• AuditPublishingResource (/auditPublishing/*, inter-server) has no OpenAPI annotations
• PublishQueueResource.deleteAssetsByIdentifiers (PublishQueueResource:40) has @Tag but no @Operation content and the form lacks @Schema
• PushPublishFilterResource POST/PUT/DELETE methods have implicit OpenAPI only (no @Operation / @ApiResponse)

Proposed change

Two-pass plan:

Pass 1 — OpenAPI hardening (no behavior change)

Add @Operation, @ApiResponse, and @Schema annotations to:

• BundleResource — every endpoint with missing or incomplete OpenAPI metadata
• AuditPublishingResource — full annotations
• PublishQueueResource.deleteAssetsByIdentifiers + DeletePPQueueElementsByIdentifierForm
• PushPublishFilterResource POST/PUT/DELETE

Regenerate dotCMS/src/main/webapp/WEB-INF/openapi/openapi.yaml and commit.

Pass 2 — Consolidation into v1

For each row in the table above, add the v1 equivalent and mark the legacy endpoint @Deprecated with @Operation(deprecated = true). Legacy endpoints keep working for one release cycle, then are removed.

Acceptance criteria

• Pass 1: every endpoint listed has full OpenAPI annotations and a CI build that regenerates the yaml matches the committed file
• Pass 2: each new v1 endpoint has parity with the legacy behavior and is covered by an integration test
• The new Angular portlet (#36040) is updated to call the v1 endpoints where available
• Deprecation notice in the openapi descriptions points to the v1 replacement

Source links

• Spike audit: #36039
• FE consumer: #36040
• Epic: #34734

Start by reading BundleResource, AuditPublishingResource, PublishQueueResource, and PushPublishFilterResource, then inspect the OpenAPI regeneration workflow and the existing v1 publishing endpoints. Done means the listed endpoints have complete metadata, the committed openapi.yaml regenerates cleanly, v1 replacements have integration-test parity, the Angular portlet uses them, and legacy routes document their deprecations.