HTTP method validation for the transaction bundle request.

[v-aljagtap]

Description

• Added validation to ensure the HTTP method in the Request component of the transaction bundle is a valid HTTPVerb enum value.

• If the HTTP method is invalid or null, a RequestNotValidException is thrown with a 400 Bad Request status and an error message.

Related issues

Addresses issue #AB 130262.

Testing

We checked the upload of the transaction bundle to the FHIR server, using the invalid request method type 'PUT''.
Result - Operation failed, and status code of 400 Bad Request is returned with error message.

We tested other HTTP operations, including the bundle containing the 'PUT'', 'GET'', 'POST'', and 'DELETE'' request methods. In all scenarios, it returned a 400 Bad Request with error message.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)