Include operation ID for the async mechanism

[jgarciahospital]

What type of PR is this?

• enhancement/feature

What this PR does / why we need it:

Add async operationId for API consumers to track async responses.

Which issue(s) this PR fixes:

Fixes #61

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.03s
✅ OPENAPI	spectral	1		0	1.83s
✅ REPOSITORY	git_diff	yes		no	0.03s
✅ REPOSITORY	secretlint	yes		no	0.8s
✅ YAML	yamllint	1		0	0.46s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[bigludo7]

Thanks Jorge.
I think we should document a bit this operationId in the documentation / Notification URL and token part no?
We have just to indicate that in case of async pattern an operationId must be sent in the 204 response and then once the 'real' result in send back asynchronously via a notification this operationId must be part of the notification to allow API consumer to "connect the dots".
WDYT?

[jgarciahospital]

Thanks Jorge. I think we should document a bit this operationId in the documentation / Notification URL and token part no? We have just to indicate that in case of async pattern an operationId must be sent in the 204 response and then once the 'real' result in send back asynchronously via a notification this operationId must be part of the notification to allow API consumer to "connect the dots". WDYT?

Thanks ludo for the proposal, description included!

[bigludo7]

LGTM !

[jlurien]

Suggested change

	When an asynchronous response is requested, the 202 response of the API will include with an `operationId` property, this `operationId` will
	When an asynchronous response is requested, the 202 response of the API will include an `operationId` property. This `operationId` property will

[bigludo7]

Thanks !

[jgarciahospital]

@sachinvodafone @bigludo7 PR reviewed and errors fixed, can be validated and merged