proposal on how to store more info in the openapi.json

[Matsemann]

I just typed this change out here in github, not spending too much time on it if it's not popular ;)

Idea is to generate openapi.json on the form of

        "/api/v1/picking_oee/{some_id}/tasks/some-action/": {
            "put": {
                "operationId": "some-action",
                "description": "...",
                "tags": [
                    "picking"
                ],
                "x-reverse-path": "api:picking_oee:some-action", <----==== the new thingy

so that I in some other generator-code later can see that this is actually not just the picking module (which the tag is), but the specific sub-module in the reverse-path, with arbitrary many levels of something:something:something

[danielkjellid]

This looks good to me! The key is also clear and representative in terms of the data it holds, but let's get Sigurd's opinion on it as well.

[ljodal]

👌