Add test devfile registry deployment to index generator testing workflow

[michael-valdron]

/kind user-story

Which area is this user story related to?

/area registry

User Story

As a devfile maintainer I want there to be no linkage between testing content and live content, so that none of the test cases break on live changes.

To best counter changes in the live devfile content not breaking parent parsing tests, it would be best to have the parent devfiles as testing content as well in a separate test devfile registry deployment.

Acceptance Criteria

• Include setup step in workflow to deploy minikube
• Create a test script to include the follow:
  • Builds devfile-index image with test parent devfile stacks
  • Deploys devfile registry using the built devfile-index image
  • Waits for devfile registry to become ready with timeout
  • If successfully deployed, runs go test ./... to start the index generator testing
• Change child devfile testing content for parent parsing to refer to the test devfile registsry instead of staging
• Include minikube in testing prerequisites for index generator

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.