Fix #1765: NextStep: Missing securitySchemes in swagger

[jnpsk]

When the Next Step is configured with powerauth.nextstep.security.auth.type=OIDC, it is expected an access token is included in the request header. This PR enhances the generated swagger, when the auth type is set to OIDC as follows:

security:
    - bearerAuth: []
    
components:
    securitySchemes:
        bearerAuth:
            type: http
            scheme: bearer
            bearerFormat: JWT

In case of powerauth.nextstep.security.auth.type=NONE (by default), no change is visible.

[zcgandcomp]

Question: this will apply the security to all endpoints (in swagger). The /api/service/status is always permitted, but we can probably ignore this...

[jnpsk]

This annotation overrides the global security requirement settings in swagger. It adds security: [] for the endpoint, which stands for no security.

"/api/service/status": {
    "get": {
        "responses": {
            ...
        },
        "security": []
    }
}

[jnpsk]

However, after double-check, the security: [] is present also in the case of powerauth.nextstep.security.auth.type=NONE for the particular endpoint only. If we would like to avoid specifying "no security" for the endpoint, when globally there is no security required, it would be necessary to solve it dynamically too.

[zcgandcomp]

It is not "nice", but technically correct there is no security for this endpoint. So we can use it.