Some small improvements to docs and tools around running tests locally against real services

[markfields]

Description

• Update getkeys instructions based on additional required step in the prompt flow
• Add inputs for providing secrets when running e2e tests against real services

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  170138 links
    1596 destination URLs
    1825 URLs ignored
       0 warnings
       0 errors

[markfields]

@Abe27342 I guess this will block the fallthrough to the local environment variables, so probably shouldn't merge this as-is. Any ideas on how to organize/implement this to make it quick/easy to plug them in on CodeSpaces or another place where getkeys hasn't been run on the local machine?