[Asset sync] Update documentation (Azure#28041)

Author: mccoyp

doc/dev/recording_migration_guide.md

@@ -60,7 +60,7 @@ Invoke-WebRequest -OutFile "generate-assets-json.ps1" https://raw.githubusercont
 - [PowerShell Core][powershell] >= 7.0 is installed.
 - [Docker][docker] or [Podman][podman] is installed.
 - Global [git config settings][git_setup] are configured for `user.name` and `user.email`.
-  - These settings can be overridden with environment variables `GIT_COMMIT_EMAIL` and `GIT_COMMIT_OWNER`, respectively.
+  - These settings can be overridden with environment variables `GIT_COMMIT_OWNER` and `GIT_COMMIT_EMAIL`, respectively.
 - The environment variable `GIT_TOKEN` is set to a valid [personal access token][git_token] for your user.
   - This token is necessary for authenticating git requests made in a Docker/Podman container.
 - Membership in the `azure-sdk-write` GitHub group.

doc/dev/test_proxy_migration_guide.md

@@ -20,6 +20,7 @@ Please refer to the [troubleshooting guide][troubleshooting] if you have any iss
   - [Fetch environment variables](#fetch-environment-variables)
   - [Record test variables](#record-test-variables)
 - [Migrate management-plane tests](#migrate-management-plane-tests)
+- [Next steps](#next-steps)
 - [Advanced details](#advanced-details)
   - [What does the test proxy do?](#what-does-the-test-proxy-do)
   - [How does the test proxy know when and what to record or play back?](#how-does-the-test-proxy-know-when-and-what-to-record-or-play-back)
@@ -348,6 +349,13 @@ instead of AzureRecordedTestCase.
 The rest of the information in this guide applies to management-plane packages as well, except for possible specifics
 regarding test resource deployment.
 
+## Next steps
+
+Once your tests have been migrated to the test proxy, they can also have their recordings moved out of the
+`azure-sdk-for-python` repo. Refer to the [recording migration guide][recording_migration] for more details.
+
+After recordings are moved, you can refer to the instructions in [`tests.md`][tests_md] to manage them.
+
 ## Advanced details
 
 ### What does the test proxy do?
@@ -507,6 +515,7 @@ client to the test.
 [pytest_setup]: https://docs.pytest.org/xunit_setup.html
 [pytest_using_fixtures]: https://docs.pytest.org/latest/how-to/fixtures.html#how-to-fixtures
 
+[recording_migration]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/recording_migration_guide.md
 [rg_preparer]: https://github.com/Azure/azure-sdk-for-python/blob/main/tools/azure-sdk-tools/devtools_testutils/resource_testcase.py
 
 [sanitizers]: https://github.com/Azure/azure-sdk-tools/blob/main/tools/test-proxy/Azure.Sdk.Tools.TestProxy/README.md#session-and-test-level-transforms-sanitiziers-and-matchers
@@ -515,6 +524,7 @@ client to the test.
 
 [tables_preparers]: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/tables/azure-data-tables/tests/preparers.py
 [test_resources]: https://github.com/Azure/azure-sdk-for-python/tree/main/eng/common/TestResources#readme
+[tests_md]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/tests.md#run-tests-with-out-of-repo-recordings
 [troubleshooting]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/test_proxy_troubleshooting.md
 
 [variables_api]: https://github.com/Azure/azure-sdk-tools/tree/main/tools/test-proxy/Azure.Sdk.Tools.TestProxy#storing-variables

doc/dev/tests.md

@@ -378,6 +378,17 @@ to the process of updating recordings.
 
 #### Update test recordings
 
+##### Environment prerequisites
+
+- The targeted library is already migrated to use the test proxy.
+- Git version > 2.25.0 is to on the machine and in the path. Git is used by the script and test proxy.
+- [Docker][docker_install] or [Podman][podman] is installed.
+- Global [git config settings][git_setup] are configured for `user.name` and `user.email`.
+  - These settings are also set with environment variables `GIT_COMMIT_OWNER` and `GIT_COMMIT_EMAIL`, respectively (in your environment or your local `.env` file).
+- The environment variable `GIT_TOKEN` is set to a valid [personal access token][git_token] for your user (in your environment or your local `.env` file).
+  - This token is necessary for authenticating git requests made in a Docker/Podman container.
+- Membership in the `azure-sdk-write` GitHub group.
+
 Test recordings will be updated if tests are run while `AZURE_TEST_RUN_LIVE` is set to "true" and
 `AZURE_SKIP_LIVE_RECORDING` is unset or "false". Since the recordings themselves are no longer in the
 `azure-sdk-for-python` repo, though, these updates will be reflected in a git-excluded `.assets` folder at the root of
@@ -709,6 +720,8 @@ Tests that use the Shared Access Signature (SAS) to authenticate a client should
 
 [generate_sas]: https://github.com/Azure/azure-sdk-for-python/blob/bf4749babb363e2dc972775f4408036e31f361b4/tools/azure-sdk-tools/devtools_testutils/azure_recorded_testcase.py#L196
 [generate_sas_example]: https://github.com/Azure/azure-sdk-for-python/blob/3e3fbe818eb3c80ffdf6f9f1a86affd7e879b6ce/sdk/tables/azure-data-tables/tests/test_table_entity.py#L1691
+[git_setup]: https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup
+[git_token]: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
 
 [kv_test_resources]: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/keyvault/test-resources.json
 [kv_test_resources_outputs]: https://github.com/Azure/azure-sdk-for-python/blob/fbdb860630bcc13c1e355828231161849a9bd5a4/sdk/keyvault/test-resources.json#L255