Draft: Illustrate scanning repository for testcases

What does this MR do and why?

This MR is less of a proof of concept and more of an illustration of scanning a project repository for test cases.

This is done as part of the consideration for this issue: https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/1423

Describe in detail what your merge request does and why.

• adds an endpoint to scan a project repository folder, specifically for Gherkin (.feature) scenarios, and populate new test cases with them.

Major considerations that aren't addressed in this MR.

• Performance thoughts

  • Use redis job queues to asynchronously complete the scan
  • Persist metadata regarding a scan to a table, and provide an endpoint to check on the status.

• Security thoughts

  • escape feature file output to avoid stored XSS.
  • Ensure parsing doesn't have any vulnerabilities.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.