[PIDM-919] mitigation: Restoring the regulationDate field to datetime format via operation policy

[cap-ang]

List of Changes

• An operation policy has been added to add the time to the date format in the regulationDate field.

Updated API:

1. PSP Get single draft flow related to the PSP, searching by name -> /fdr-psp/service/v1/psps/{pspId}/created/fdrs/{fdr}/organizations/{organizationId}
2. PSP Get single published flow related to the PSP, searching by name and revision -> /fdr-psp/service/v1/psps/{pspId}/published/fdrs/{fdr}/revisions/{revision}/organizations/{organizationId}
3. EC Get single published flow related to creditor institution, searching by name and revision -> /fdr-org/service/v1/organizations/{organizationId}/fdrs/{fdr}/revisions/{revision}/psps/{pspId}

Motivation and Context

The microservice starting from this PR handles the regulationDate as a date. To overcome this limitation and comply with SANP3.9.1, the regulationDate in Orgs API response is modified to become a date-time.

How Has This Been Tested?

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]

This pull request does not contain a valid label. Please add one of the following labels: [major, minor, patch, patch, skip]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pasqualespica]

lgtm @cap-ang only 1thing.
Put Mitigation keyword into PR title, as reminder to us that this mitigation should be removed after SANP 3.10 was published and "implemented" by EC that open issue