idDocument Management Error Scenarios

[PedroDiez]

What type of PR is this?

• enhancement
• tests

What this PR does / why we need it:

This PR manages a simplification for some error scenarios:

• idDocument is required by API Provider and is not provided. Current exception: 422 -CUSTOMER_INSIGHTS.ID_DOCUMENT_REQUIRED
• idDocument (required) and phoneNumber provided do not point the same susbcription: Current exception: 422 - CUSTOMER_INSIGHTS.INVALID_IDENTIFIERS

Both scenarios are covered by 422 - SERVICE_NOT_APPLICABLE exception

Regarding tests, the following ones are updated accordingly:

@retrieve_scoring_422.02_identifiers_mismatch
@retrieve_scoring_422.07_id_document_required_three_legged
@retrieve_scoring_422.08_id_document_required_two_legged
@retrieve_scoring_422.09_id_document_required_three_legged_with_scoring_type
@retrieve_scoring_422.10_id_document_required_two_legged_with_scoring_type

Taking advantage some clarifications are provided for tests:
@retrieve_scoring_C02.01_phone_number_not_schema_compliant
@retrieve_scoring_404.01_idDocument_not_found

Which issue(s) this PR fixes:

Fixes #59

Special notes for reviewers:

Changelog input

 iDocument management error scenarios enhacements

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.01s
✅ API	spectral	1		0	1.61s
✅ GHERKIN	gherkin-lint	1		0	0.38s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	secretlint	yes		no	0.63s
✅ YAML	yamllint	1		0	0.32s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[KevScarr]

All happy - as per review call 422 SERVICE_NOT_APPLICABLE added to cater for mismatch on phoneNumber and idDocument.