chore: adopt markdownlint and markdown-table-formatter for *.md (#15831)

Co-authored-by: Edward Angert <EdwardAngert@users.noreply.github.com>

docs/tutorials/configuring-okta.md

@@ -4,7 +4,7 @@
   <span style="vertical-align:middle;">Author: </span>
   <a href="https://github.com/Emyrk" style="text-decoration: none; color: inherit; margin-bottom: 0px;">
     <span style="vertical-align:middle;">Steven Masley</span>
-    <img src="https://avatars.githubusercontent.com/u/5446298?v=4" width="24px" height="24px" style="vertical-align:middle; margin: 0px;"/>
+    <img src="https://avatars.githubusercontent.com/u/5446298?v=4" alt="Steven Masley" width="24px" height="24px" style="vertical-align:middle; margin: 0px;"/>
   </a>
 </div>
 December 13, 2023
@@ -22,7 +22,7 @@ roles.
 
 You may use a hybrid of the following approaches.
 
-# (Easiest) Sync using Okta Groups
+## (Easiest) Sync using Okta Groups
 
 If the Coder roles & Coder groups can be inferred from
 [Okta groups](https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-about-groups.htm),
@@ -67,7 +67,7 @@ CODER_OIDC_USER_ROLE_FIELD=groups
 CODER_OIDC_USER_ROLE_MAPPING='{"admin-group":["template-admin","user-admin"]}'
 ```
 
-# (Easy) Mapping Okta profile attributes
+## (Easy) Mapping Okta profile attributes
 
 If roles or groups cannot be completely inferred from Okta group memberships,
 another option is to source them from a user’s attributes. The user attribute
@@ -105,7 +105,7 @@ CODER_OIDC_USER_ROLE_MAPPING='{"admin-group":["template-admin","user-admin"]}'
 # CODER_OIDC_GROUP_FIELD=...
 ```
 
-# (Advanced) Custom scopes to retrieve custom claims
+## (Advanced) Custom scopes to retrieve custom claims
 
 Okta does not support setting custom scopes and claims in the default
 authorization server used by your application. If you require this