[PAGOPA-2446] refactoring: Update status on-the-fly

[cap-ang]

List of Changes

TL;DR

• validityCheckAndUpdate method has been added 🆕 -> It is used when Get and Pay Payment Option

• expirationCheckAndUpdate method has been added 🆕 -> It is used only when Get Payment Option

• Check on expiration or validity on report API has been removed 🗑️

These scenarios were refactored:

[GET PO by NAV scenario]

• check validity (if published and now > validityDate) -> update
• check expiration (if switchToExpired and valid and > now) -> update

[PAY scenario]

• check validity (if published and now > validityDate) -> update
• expiration check is useless (pay already done)

[INVALIDATE scenario]

• check expiration because expired isn't an invalidable status
• validity check is useless (both published and valid are invalidable status)

Motivation and Context

Refactoring status retrieve on the fly handling. Cron granularity differs from validityDate and dueDate granularity. These changes helps to update status on-the-fly.

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.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

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

[pasqualespica]

great work 🚀

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud