Fixes examples for compliance with RFC-9535

[mikekistler]

This PR makes a few minor fixes to the overlay examples to ensure they are compliant with RFC-9535.

I tested all the examples in the spec with Speakeasy's overlay playground and only these two had problems.

Note that any examples that use filters need

x-speakeasy-jsonpath: rfc9535

but I did not include that in the examples.

[lornajane]

Thanks!

[kevinswiber]

@mikekistler @gregsdennis Will this query work if we keep the original x-oai-traits example?

$.paths[[email protected]['x-oai-traits'][?@ == 'paged']].get

openapi: 3.1.0
info:
  title: API with a paged collection
  version: 1.0.0
paths:
  /items:
    get:
      x-oai-traits: ['paged']
      responses:
        200:
          description: OK

EDIT: It appears to work with Speakeasy's tooling.

[gregsdennis]

Yeah, that's compliant @kevinswiber.

[mikekistler]

Thanks @kevinswiber and @gregsdennis for puzzling out how to use the original x-oai-traits with array value. I've updated the PR to incorporate this.

[lornajane]

I'm happy to approve this but we still have some requested changes to look at.

[ralfhandl]

@mikekistler Please re-target to main, changing file versions/1.1.0-dev.md - might require copying the changed file to a new branch off main.

[mikekistler]

I have rebased on main and moved the changes to versions/1.1.0-dev.md.

@ralfhandl @baywet this is ready for re-review.

[gregsdennis]

This change isn't necessary for RFC-9535, but it would increase the compatibility with legacy libraries.