Deploy docs to a new folder named after their tagged version

[santisoler]

• Make deployment stage to depend on DocBuild
• Store discretize version in a variable
• Update latest symlink

TODO:

• Replace the latest folder by a symlink in simpeg/discretize-docs repo before merging this PR.
• Remove the "experimental" stage I created to check if the version variable can be read in another stage.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.25%. Comparing base (707e31f) to head (5847785).
Report is 15 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #372   +/-   ##
=======================================
  Coverage   86.25%   86.25%           
=======================================
  Files          89       89           
  Lines       18695    18695           
  Branches     2959     2959           
=======================================
  Hits        16125    16125           
  Misses       1884     1884           
  Partials      686      686           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jcapriot]

Ok, this should work now. I put in three base pipeline level variables that all stages have access to.

• BRANCH_NAME
• IS_TAG
• IS_MAIN
  It creates a folder based on BRANCH_NAME, which is main for main, and the name of the tag for release versions (e.g. v0.10.0), and avoids the awkward python call to the installed discretize version.

[jcapriot]

Let's merge and see what breaks!