Create TARDIS release workflow

[epassaro]

Description

This is the workflow that creates the TARDIS release on GitHub.

• It's quite similar to the previous one.
• It's triggered by merging a pull request from a branch starting with the words pre-release-20 to master or manually
• Upload the new .lock files as assets

Motivation and context

How has this been tested?

• Testing pipeline.
• Other.

Not tested, let's merge and see.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[codecov]

Codecov Report

Merging #1999 (c0f828f) into master (713c9db) will not change coverage.
The diff coverage is n/a.

❗ Current head c0f828f differs from pull request most recent head e301002. Consider uploading reports for the commit e301002 to get more accurate results

@@           Coverage Diff           @@
##           master    #1999   +/-   ##
=======================================
  Coverage   59.99%   59.99%           
=======================================
  Files          70       70           
  Lines        8111     8111           
=======================================
  Hits         4866     4866           
  Misses       3245     3245           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more