Resolve "sso_quickstart.md is blank"

Docs Merge Request

Changes

• fixed hyperlink markdown syntax issue with quickstart.md
• sso_quickstart.md was accidentally deleted / made blank, reverted that change to restore it. (the following are additional changes after restoring the sso_quickstart.md, which won't correctly show up as a diff, since it was accidentally deleted.)
• updated logic so BIG_BANG_VERSION would reference a latest version instead of a pinned version, added a comment about how to pin to a version + the last version the guide was tested against.
• updated dependencies k3d, helm, kustomize, kubectl to same versions the quickstart.md had recently been updated to.
• updated k3d cluster create flags to account for breaking changes from k3d v4.x -> v5.x
• removed --values $HOME/bigbang/docs/example_configs/opa-overrides-k3d.yaml reference to external file, and instead embedded the contents of that file in the how to guide, should be more resilient incase the file ever gets renamed or moved.
• corrected a | sudo tee -a ~/.ssh/config --to be--> | tee -a ~/.ssh/config after realizing an edge case where it'd fail + that it wasn't needed.
• re-added valid wildcard ingress cert into keycloak's values (it had been moved to a new location, which means this how to guide was probably broken for a few months until this refresh occurred.)
• split some long markdown sections in 2, and removed apostrophes in some sections to improve ability to copy paste.

Note:

I did an E2E retest of the guide after finishing all commits / tweaks.

Preview of Changed markdown file

Current

https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/docs/guides/deployment_scenarios/quickstart.md

Changes

https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/1134-update-sso-quickstart/docs/guides/deployment_scenarios/sso_quickstart.md

For Issue

Closes #1134 (closed)

docs/guides/deployment_scenarios/quickstart.md

@@ -46,7 +46,7 @@ Important limitations of this quick start guide's implementation of k3d to be aw
   * Multiple Ingress Gateways makes a demoable/tinkerable KeyCloak and locally hosted SSO deployment much easier.
   * Multiple Ingress Gateways can be demoed on k3d if configuration tweaks are made, MetalLB is used, and you are developing using a local Linux Desktop. (network connectivity limitations of the implementation would only allow a the web browser on the k3d host server to see the webpages.)
   * If you want to easily demo and tinker with Multiple Ingress Gateways and Keycloak, then MetalLB + k3s (or another non-Dockerized Kubernetes distribution) would be a happy path to look into. (or alternatively create an issue ticket requesting prioritization of a keycloak quick start or better yet a Merge Request.)
-* Access to Container Images Prerequisite is satisfied by using personal image pull credentials and internet connectivity to <registry1.dso.mil>
+* Access to Container Images Prerequisite is satisfied by using personal image pull credentials and internet connectivity to <https://registry1.dso.mil>
 * Customer Controlled Private Git Repo Prerequisite isn't required due to substituting declarative git ops installation of the Big Bang Helm chart with an imperative helm cli based installation.
 * Encrypting Secrets as code Prerequisite is substituted with clear text secrets on your local machine.
 * Installing and Configuring Flux Prerequisite: Not using GitOps for the quick start eliminates the need to configure flux, and installation is covered within this guide.
@@ -100,7 +100,7 @@ The following requirements are recommended for Demonstration Purposes:
       User ubuntu
       StrictHostKeyChecking no   #Useful for vagrant where you'd reuse IP from repeated tear downs
     #########################"""
-    echo "$temp" | sudo tee -a ~/.ssh/config  #tee -a, appends to preexisting config file
+    echo "$temp" | tee -a ~/.ssh/config  #tee -a, appends to preexisting config file
     ```
 
 1. SSH to instance