Make small improvements to the documentation

[james-garriss]

🗣 Description

I made the following changes to improvement the documentation:

• Fixed 404 on Execution
• Converted results on Reports into a table for better readability
• Removed extra space on Parameters
• Replaced with johndoe on Dependencies (and others) for better render.
• Clarified purpose of commented out product values in Typical Use section of Configuration.
• Fixed hyperlink on Execution to jump directly to ProductNames

💭 Motivation and context

Closes #1154
Closes #1156

🧪 Testing

Previewed changes in VSCode.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• Related issues these changes resolve are linked preferably via closing keywords.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.
• Feature branch has been rebased against changes from parent branch, as needed
• Resolved all merge conflicts on branch
• Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[james-garriss]

@nanda-katikaneni , this one is ready (again)