feat: add CrateDB OpenAPI specs

[Rahuljagwani]

@uniqueg As told, this PR contains only OpenAPI specifications.

Summary by Sourcery

This pull request adds OpenAPI specifications for the crate_db microservice, providing detailed documentation for endpoints related to managing RO-Crates and service information.

• New Features:
  • Introduced OpenAPI specifications for the crate_db microservice, detailing endpoints for managing RO-Crates and service information.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request introduces a new OpenAPI specification file for the crate_db microservice. The specification includes endpoints for managing RO-Crates and service information, along with detailed request and response schemas. It also defines common error responses for various HTTP status codes.

File-Level Changes

Files	Changes
crate_db/api/specs/crate_db_specs.yaml	Introduced a comprehensive OpenAPI specification for the crate_db microservice, detailing endpoints, request/response schemas, and error handling.

---

Tips

- Trigger a new Sourcery review by commenting `@sourcery-ai review` on the pull request. - You can change your review settings at any time by accessing your [dashboard](https://sourcery.ai/dashboard): - Enable or disable the Sourcery-generated pull request summary or reviewer's guide; - Change the review language; - You can always [contact us](mailto:support@sourcery.ai) if you have any questions or feedback.

[Rahuljagwani]

Issues in previous PR:

• Problem: Previously the name of the schema containing service specs was Service and the schema itself was redundant.(Link) Fix: The name of the service was changed to ROCServiceInfo and allof was used in schema.(Link)

• Problem: The whole request body was being sent in response again for POST operations.(Link) Fix: This was shortened the response to a message.(Link)

  • Problem: Use of x-body-name. Link Fix: It was removed from everywhere.

• Problem: No custom messages and status code in Errors(eg. BadRequest, etc.) Link Fix: Solved by adding custom messages and status code in the respective errors. Link

  • Problem: Unnecessary parameters in ProblemDetails schema. Link Fix: Limited to title and status only. Link

  • Problem: Unnecessary errors (404 and 400) for GET operation Fix: Removed

  Other than above, the descriptions and messages have been shortened down for the sake of consistency.