ci: pointing to correct versioned yaml on website creation

[JaydipGabani]

What this PR does / why we need it:
Correctly updates the install command to point to appropriate versions in website.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #

Special notes for your reviewer:

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.14%. Comparing base (6d1e4ee) to head (ea2b9dc).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3258      +/-   ##
==========================================
- Coverage   54.28%   54.14%   -0.15%     
==========================================
  Files         134      134              
  Lines       12356    10253    -2103     
==========================================
- Hits         6707     5551    -1156     
+ Misses       5152     4196     -956     
- Partials      497      506       +9     

Flag	Coverage Δ
unittests	54.14% <ø> (-0.15%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[ritazh]

LGTM

[JaydipGabani]

@ritazh @maxsmythe @sozercan This change sould now handle patching docs for subsequent minor release patches as well.

[sozercan]

is it possible to avoid a second pr? why can't we do this in the same pr for the beta release?

[JaydipGabani]

the beta PR only gets released on a new minor version release, and docs changes are included with that. However, the patch-doc workflow is specifically for subsequent patch versions for which we do not update beta.

[JaydipGabani]

@sozercan are we good to merge this?