I haven't checked it out, but this would be something which can be discussed as part of the Connexion 3.0 roadmap (#1395).

I would say this one is blocked by swagger-api/swagger-ui#5891
At least if the resulting API is meant to be documented using Swagger UI.

It might also depend on python-jsonschema/jsonschema#782 / python-jsonschema/jsonschema#817, given the full alignment of OpenAPI 3.1.0 with JSON Schema draft 2020-12.

There may also be required changes in https://github.com/p1c2u/openapi-spec-validator. For example python-openapi/openapi-spec-validator#111 (which is based on a draft of OpenAPI spec 3.1).

it seems like both mentioned dependencies were completed

Yes, maybe also the bundled SwaggerUI needs to be updated to 5.x supporting OpenAPI 3.1.0

Is it possible for the maintainers to explain their vision for support of OpenAPI 3.1?

Do the maintainers know what changes would be necessary to support OpenAPI 3.1 and/or would be open to collaborating on making those changes?

I do not have a good view of what would be needed to support OpenAPI 3.1.

We have a Specification class which has an implementation for Swagger 2 and OpenAPI 3. A good starting point would be to provide an implementation for OpenAPI 3.1 and check if additional changes are needed.

This would be welcomed as a contribution.