fix for release task

[epassaro]

Description

• Use inline option in release task, see this issue.
• Added helper scripts to make pipeline more readable (and maintainable). Tested and working, see here.
• Hide azure-pipelines folder (requires immediate action after merging).

Motivation and context

The pipeline was broken due to incorrect information displayed on Microsoft Azure's documentation.

How has this been tested?

• Testing pipeline.
• Other.

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 #1786 (5427618) into master (575002c) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master    #1786   +/-   ##
=======================================
  Coverage   58.42%   58.42%           
=======================================
  Files          66       66           
  Lines        6684     6684           
=======================================
  Hits         3905     3905           
  Misses       2779     2779           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 575002c...4f3f94a. Read the comment docs.

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.