[BUG] Superseded operations paths do not align with defined paths

[Xtansia]

What is the bug?

The paths defined in the _superseded_operations.yaml do not match with the paths defined in the rest of the spec.

For example:
In _superseded_operations.yaml we have:

/_opendistro/_security/api/internalusers/{name}:
  superseded_by: /_plugins/_security/api/internalusers/{name}
  operations:
    - GET
    - PUT
    - DELETE
    - PATCH

However in namespaces/security.yaml we have:

paths:
  /_plugins/_security/api/internalusers/{username}:
    get:
      operationId: security.get_user.0
      x-operation-group: security.get_user
      x-version-added: '1.0'
      description: Retrieve one internal user.
      externalDocs:
        url: https://opensearch.org/docs/latest/security/access-control/api/#get-user
      parameters:
        - $ref: '#/components/parameters/security.get_user::path.username'
      responses:
        '200':
          $ref: '#/components/responses/security.get_user@200'

The path parameter names do not match, which means on merging we get:

paths:
  /_opendistro/_security/api/internalusers/{name}:
    get:
      operationId: security.get_user.0_superseded
      x-operation-group: security.get_user
      x-version-added: '1.0'
      description: Retrieve one internal user.
      externalDocs:
        url: https://opensearch.org/docs/latest/security/access-control/api/#get-user
      parameters:
        - $ref: '#/components/parameters/security.get_user::path.username'
        - $ref: '#/components/parameters/_global::query.pretty'
        - $ref: '#/components/parameters/_global::query.human'
        - $ref: '#/components/parameters/_global::query.error_trace'
        - $ref: '#/components/parameters/_global::query.source'
        - $ref: '#/components/parameters/_global::query.filter_path'
      responses:
        '200':
          $ref: '#/components/responses/security.get_user@200'
      deprecated: true
      x-ignorable: true

This means the final spec is incorrect as the path specifies {name} but we only provide a path param named username