Now will distinguish between status codes the expected inferred type

[Boxap]

Fixes #1956 and #1850 .
(this is a duplicate of PR #1957 by carloscbl. Test failed in original PR)

The test outputs that showed a failure have expired. Please rebase etc. and push, then hopefully the Github workflow will run again here. Thanks.

Changes proposed in this pull request:

• Now instead merging 2 different responses as available options, will check for the status code the available options, after that if you still have multiple content types it will raise the error, and users should specify in headers the correct one

[chrisinmtown]

Did you run tox locally before you created this PR? I pulled this branch, ran tox and I see many, many failures. For example:

============================================================= FAILURES ==============================================================
___________________________________________ test_headers_produces[swagger.yaml-FlaskApp] ____________________________________________

simple_app = <connexion.apps.flask.FlaskApp object at 0x1058d7380>

    def test_headers_produces(simple_app):
        app_client = simple_app.test_client()
    
        response = app_client.post("/v1.0/goodevening/dan", data={})
>       assert response.status_code == 201
E       assert 500 == 201
E        +  where 500 = <Response [500 Internal Server Error]>.status_code

tests/api/test_headers.py:17: AssertionError
------------------------------------------------------- Captured stderr call --------------------------------------------------------
INFO:connexion.middleware.swagger_ui:Adding spec json: /v1.0/swagger.json
ERROR:connexion.middleware.exceptions:NonConformingResponseHeaders(status_code=500, detail="Invalid Response Content-type (application/json), expected ['text/plain']")
--------------------------------------------------------- Captured log call ---------------------------------------------------------
INFO     connexion.middleware.swagger_ui:swagger_ui.py:80 Adding spec json: /v1.0/swagger.json
ERROR    connexion.middleware.exceptions:exceptions.py:79 NonConformingResponseHeaders(status_code=500, detail="Invalid Response Content-type (application/json), expected ['text/plain']")
========================================================= warnings summary ==========================================================

[Boxap]

@chrisinmtown nope, originally I just copied the PR from carloscbl, because in that PR the blocker was that test outputs expired. Now I checked the tests and fixed the problems

[chrisinmtown]

Please add a test case for this new code. Your PR changes a behavior you didn't like and which no tox test found. Anyhow, the existing tox cases all pass for me. The code coverage improves by a tiny amount :)

Is this behavior documented at all? It seems to me maybe this could be explained in https://github.com/spec-first/connexion/blob/main/docs/response.rst I didn't find anything about custom responses or inferred content-type values there yet.

[Boxap]

@chrisinmtown Done

[chrisinmtown]

Wow that was a quick response, thanks for adding doc and tests. One more thing, you probably want to squash your commits down to just one with a nice message that explains all the work you did.

Anyhow I pulled the latest from your repo and the tox tests pass for python 3.9..3.12 so I approved this PR, for what little that means lol.

@Ruwann @RobbeSneyders would you please approve a GitHub workflow run on this PR?

[chrisinmtown]

Do you want to leave the single quotes off this path, to match the existing style?