[SELC-6174] feat: rework onboarding completion logic

[gianmarcoplutino]

List of Changes

-set status to REQUEST in Onboarding completion APIs

Motivation and Context

This change is necessary as SM will first have to create an onboarding request and then invoke another API to load the signed agreement and complete the same request. Here the logic has been revised so that in the case of invoking the API the request is put in Request and the Request phase is executed which includes creation of the contract and saving of the Token on the DB also in the workflowType CONFIRMATION

How Has This Been Tested?

the local ms was started and the api was invoked and onboarding was subsequently completed

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
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