Doc updates for "FIPS 140-2 in Contour"

[moeyui1]

Some updates for FIPS 140-2 in Contour, see also #4794 :

1. Add description for Go 1.19+ to enable integrating BoringCrypto;
2. Add rsc.io/goversion as an another way to validate whether the contour binary has been compiled with BoringCrypto.

Closes #4794.

[codecov]

Codecov Report

Merging #4813 (d9bb096) into main (a256481) will decrease coverage by 0.13%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4813      +/-   ##
==========================================
- Coverage   76.09%   75.95%   -0.14%     
==========================================
  Files         140      139       -1     
  Lines       16895    16855      -40     
==========================================
- Hits        12857    12803      -54     
- Misses       3786     3798      +12     
- Partials      252      254       +2     

Impacted Files	Coverage Δ
...ner/objects/rbac/serviceaccount/service_account.go	53.57% <0.00%> (-10.54%)	⬇️
internal/envoy/bootstrap.go	52.27% <0.00%> (-5.23%)	⬇️
internal/provisioner/objects/service/service.go	73.09% <0.00%> (-4.64%)	⬇️
internal/provisioner/objects/rbac/role/role.go	69.04% <0.00%> (-4.54%)	⬇️
...ovisioner/objects/rbac/rolebinding/role_binding.go	70.73% <0.00%> (-3.78%)	⬇️
...ts/rbac/clusterrolebinding/cluster_role_binding.go	70.73% <0.00%> (-3.78%)	⬇️
...nternal/provisioner/objects/dataplane/dataplane.go	85.68% <0.00%> (-2.20%)	⬇️
...ovisioner/objects/rbac/clusterrole/cluster_role.go	78.94% <0.00%> (-1.65%)	⬇️
...ernal/provisioner/objects/deployment/deployment.go	89.77% <0.00%> (-1.57%)	⬇️
internal/dag/httpproxy_processor.go	92.74% <0.00%> (-0.40%)	⬇️
... and 28 more

[skriss]

Thanks @moeyui1 for the updates here! One comment from me. cc @sunjayBhatia

[sunjayBhatia]

thanks for the PR @moeyui1, running through the update instructions now 👍🏽

[moeyui1]

A little busy these days, will complete this a few days later.

[github-actions]

The Contour project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 14d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the PR is closed

You can:

• Mark this PR as fresh by commenting or pushing a commit
• Close this PR
• Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

addressed