[DISCO-3134] Add Steps to CircleCI Workflow Test Jobs For Pushing Test Artifacts to the ETE GCP Cloud Storage

[Trinaa]

References

JIRA: DISCO-3134

Description

• add executors to circleci config to address schema validation errors
  • Example:
    
• rename unit and integration test artifact files to comply with ETE pipeline specifications
• add upload test artifact job to main-workflow
• remove circleci artifact storage to reduce costs
• remove coverage-combined command, since file is unused

PR Review Checklist

Put an x in the boxes that apply

• This PR conforms to the Contribution Guidelines
• The PR title starts with the JIRA issue reference, format example [DISCO-####], and has the same title (if applicable)
• [load test: (abort|skip|warn)] keywords are applied to the last commit message (if applicable)
• Documentation has been updated (if applicable)
• Functional and performance test coverage has been expanded and maintained (if applicable)

[ncloudioj]

Hey Kat, what do you think about pushing test artifacts from Actions instead from CircleCi? FWIW, we're in the process of migrating away from CircleCI.

[Trinaa]

Hey Kat, what do you think about pushing test artifacts from Actions instead from CircleCi? FWIW, we're in the process of migrating away from CircleCI.

@ncloudioj I hadn't realized that Git Actions were being using on the main workflow atm. My preference would be to merge this and then migrate it over to Git Actions so that progress on the ETE pipeline isn't blocked. Is that possible?