add versioned docs

[sozercan]

Signed-off-by: Sertac Ozercan [email protected]

What this PR does / why we need it:

• tag version for docs as part of release (e.g., make version-docs NEWVERSION=v3.7.x), see updated release doc
• this will create following files and directories that will need to be merged in with the release PR

	versioned_docs/
	versioned_sidebars/
	versions.json

• after the release PR is merged, versioned docs will be generated in website

example: https://sozercan.github.io/gatekeeper/website/docs/ (see upper right)

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 #1185

Special notes for your reviewer:

[codecov-commenter]

Codecov Report

Merging #1645 (c1747d2) into master (87cb662) will decrease coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1645      +/-   ##
==========================================
- Coverage   52.81%   52.54%   -0.27%     
==========================================
  Files          98       98              
  Lines        8591     8591              
==========================================
- Hits         4537     4514      -23     
- Misses       3695     3715      +20     
- Partials      359      362       +3     

Flag	Coverage Δ
unittests	52.54% <ø> (-0.27%)	⬇️

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

Impacted Files	Coverage Δ
pkg/readiness/list.go	79.41% <0.00%> (-11.77%)	⬇️
...onstrainttemplate/constrainttemplate_controller.go	55.21% <0.00%> (-4.51%)	⬇️

---

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 87cb662...c1747d2. Read the comment docs.

[maxsmythe]

LGTM, thank you for doing this!

[maxsmythe]

nit, use a before and after if you want to clarify (v3.6.x -> 3.7.0)

[sozercan]

updated.

[sozercan]

@maxsmythe thoughts on if we should call NEWVERSION v3.7.0 or v3.7.x?

[sozercan]

.x makes sense since ideally all patch versions shouldn't have behavior changes and it's more clear that it applies to all

[maxsmythe]

I'm okay with either. Usually a new minor version starts at patch zero, but keeping x for both is clearer.

[sozercan]

fyi @ritazh @shomron