docs(debug): Add guide on enabling Debug logs (aws#5490)

<!---
    REMINDER:
    - Read CONTRIBUTING.md first.
    - Add test coverage for your changes.
    - Update the changelog using `npm run newChange`.
    - Link to related issues/commits.
    - Testing: how did you test your changes?
- Screenshots (if the pull request is related to UI/UX then please
include light and dark theme screenshots)
-->

## License

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Signed-off-by: Nikolas Komonen <[email protected]>

Author: nkomonen-amazon

CONTRIBUTING.md

@@ -344,9 +344,6 @@ The `aws.dev.forceDevMode` setting enables or disables Toolkit "dev mode". Witho
 -   Use `getLogger()` to log debugging messages, warnings, etc.
     -   Example: `getLogger().error('topic: widget failed: %O', { foo: 'bar', baz: 42 })`
 -   Log messages are written to the extension Output channel, which you can view in vscode by visiting the "Output" panel and selecting `AWS Toolkit Logs` or `Amazon Q Logs`.
--   While viewing the Output channel (`AWS Toolkit Logs` or `Amazon Q Logs`) in vscode:
-    -   Click the "gear" icon to [select a log level](https://github.com/aws/aws-toolkit-vscode/pull/4859) ("Debug", "Info", "Error", …).
-    -   Click the "..." icon to open the log file.
 -   Use the `aws.dev.logfile` setting to set the logfile path to a fixed location, so you can follow
     and filter logs using shell tools like `tail` and `grep`. For example in settings.json,
     ```
@@ -362,6 +359,21 @@ The `aws.dev.forceDevMode` setting enables or disables Toolkit "dev mode". Witho
     -   Enter text in the Debug Console filter box to show only log messages with that text. <br/>
         <img src="./docs/images/debug-console-filter.png" alt="VSCode Debug Console" width="320"/>
 
+#### Enabling Debug Logs
+
+How to enable more detailed debug logs in the extensions.
+If you need to report an issue attach these to give the most detailed information.
+
+1. Open the Command Palette (`cmd/ctrl` + `shift` + `p`), then search for "View Logs". Choose the correct option for the extension you want, eg: `AWS: View Logs` or `Amazon Q: View Logs`
+   ![](./docs/images/logsView.png)
+2. Click the gear icon on the bottom right and select `Debug`
+   ![](./docs/images/logsSetDebug.png)
+3. Click the gear icon again and select `Set As Default`. This will ensure we stay in `Debug` until explicitly changed
+   ![](./docs/images/logsSetDefault.png)
+4. Open the Command Palette again and select `Reload Window`.
+5. Now you should see additional `[debug]` prefixed logs in the output.
+   ![](./docs/images/logsDebugLog.png)
+
 ### Telemetry
 
 -   See [docs/telemetry.md](./docs/telemetry.md) for guidelines on developing telemetry in this project.

docs/faq-credentials.md

@@ -1,4 +1,4 @@
-# FAQ / Troubleshooting
+# FAQ / Troubleshooting - Auth/SSO/Credentials
 
 ### AWS Builder ID "Invalid client provided"
 

docs/faq-debug.md

@@ -0,0 +1,5 @@
+# FAQ / Troubleshooting - Debugging/Development
+
+### Enabling Debug Logs
+
+[See steps here to enable more detailed debug logs for the extension.](../CONTRIBUTING.md#enabling-debug-logs)