Supported endpoints with the same tag as deprecated endpoints are also marked deprecated

[laurel]

As shown the in screenshot, several Async Parsing endpoints are marked "Deprecated". However, the Async Parsing JSON spec does not include `"deprecated": true` for those endpoints, or any others in that spec file.

In a different JSON file, similar endpoints (whose paths are different than the ones above) are marked with "deprecated": true, and they have the same tag ("Parsers CRUD API") as the supported endpoints in the first file.

The issue resolved after we changed the tags in the second file to ""Parsers CRUD API (Deprecated)" so they no longer match the tags in the first file:
https://lucidworks-docs-7272-fix-deprecations.mintlify.app/api-reference/parsers-crud-api/list-all-parsers

An endpoint should only be marked "Deprecated" when its operation definition contains "deprecated": true; the deprecation should not be applied to all operations with the same tag. The OpenAPI standard specifies that the deprecated key applies to individual operations: https://spec.openapis.org/oas/v3.2.0.html?utm_source=chatgpt.com#:~:text=the%20expected%20responses.-,deprecated,from%20usage%20of%20the%20declared%20operation.%20Default%20value%20is%20false.,-security

Thus we should be able to mark an individual operation as deprecated without having all of the operations in its group marked deprecated.