display "latest" in doc version

[epassaro]

Description

Motivation and context

As @jaladh-singhal pointed out, looks more "stable". The documentation pipeline builds the master branch tip, so it's a good name. Also it's the same used by RTD.

How has this been tested?

• Testing pipeline.
• Other.

Built locally.

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.

[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.

[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.

[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.

[codecov]

Codecov Report

Merging #1726 (5338d64) into master (ab967fd) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master    #1726   +/-   ##
=======================================
  Coverage   61.87%   61.87%           
=======================================
  Files          63       63           
  Lines        5852     5852           
=======================================
  Hits         3621     3621           
  Misses       2231     2231           

Impacted Files	Coverage Δ
tardis/tardis/montecarlo/spectrum.py	65.51% <0.00%> (ø)
tardis/tardis/plasma/standard_plasmas.py	73.11% <0.00%> (ø)

---

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 ab967fd...b5e18b4. Read the comment docs.

[jaladh-singhal]

Thanks for making quick PR. There's one thing we should take care of

[epassaro]

Thanks for making quick PR. There's one thing we should take care of

Done!