[PAGOPA-1832] fix: Check station related to payment notice during existing payment position analysis

[andrea-deri]

With this PR, the WISP-Converter application will include a new strategy for analyze payment positions from GPD. This strategy must execute a check on station that will be used on the Nuovo Modello Unico's payment next steps and the analysis are useful to better handle payment positions, either if they are in valid state or in invalid state. In fact, in valid state the check is related to avoid the possibility of using a station misconfigured; in invalid state the check is related to the possibility to exclude the send of paaInviaRT request to creditor institutions, but checking if the station is used for GPD onboarding.
Other changes refers to several little refactoring points, made in order to made the code more readable and avoiding duplicated strategies of data-accesses.

List of Changes

• Add explicit check on station during the analysis of existing payment positions
• Updated getRedirectURL in order to use the refactored "retrieve station from cache" method
• Refactored various section, defining common strategy for accessing to cached data and other standard data structures (like payment position's DTOs)
• Set a first definition of openapiDefinition field for AppErrorCodeMessageEnum: on next developments it will be used for extract user-friendly descriptions about the error to be set in OpenAPI specifications
• Added new parameter about GPD-Payment's endpoint, setting its placeholder on Helm in order to permit dynamic configuration

Motivation and Context

These changes are required because it is necessary to add a new check on used station

How Has This Been Tested?

Tested in local environment

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

Comment this PR with update_code to format the code. Consider to use pre-commit to format the code.