Add Teleport Cloud instructions to two guides

[ptgott]

See #10634

Restricted Sessions for SSH

While this already includes a compatibility note, I wanted to ensure
that users would only see information relevant to the scope they had
selected. Changes made:

• Added a tabbed Prerequisites section

• Removed instructions to install the Auth/Proxy that implicitly
  applied to all scopes

• Misc style/grammar/clarity edits

BPF Session Recording

• Add scoped tabs
• Merge steps 2 and 3, which both involved examining the audit log to
  verify that Enhanced Session Recording is enabled
• Misc style/grammar/clarity tweaks

[ulysseskan]

These look good to me.

This wasn't part of the changes, but I wonder if this should be changed in any example teleport.yaml config files:

  # Replace with IP of Teleport Auth server.
  - 127.0.0.1:3025

Can't the auth_servers value also be a fully qualified domain name? So they wouldn't necessarily need to use the IP. Maybe say Replace with IP or fully qualified domain name of the Teleport Auth server.

[ptgott]

@ulysseskan I've suggested using the more vague "address"

[zmb3]

Kernel or kernel? We use both in this doc and should probably choose one and be consistent.

[zmb3]

Would it make sense to only show the config block related to enhanced recording?

For example, this field can be the auth server or the proxy server. We cover this in other documentations, and going into detail about that here would distract from enhanced recording.

[ptgott]

I think the advantage of using this approach is that the user can paste everything in this snippet into the config file on the Node, make minor adjustments, and proceed to the next step, without having to navigate through the docs. The current Step 2 is incomplete, so I've fleshed it out.

[zmb3]

Note: This only applies if using a file-based event log. (Not when using S3 or other cloud storage for audit events)

[ptgott]

Added a Details section about this

[zmb3]

It feels like this section is too far down on the page. Most readers aren't going to know by default what "Enhanced Session Recording" is or why they would want it.

Should we move some or all of this to the intro before the pre-requisites so we don't lose readers?

[ptgott]

I've restored the original introductory section with some light copy-edits.

[zmb3]

Maybe reword this? The sessions are still recorded, so I'm not sure I would describe it as session recording being bypassed.

The disadvantage is really that the users true actions can be hidden or obfuscated in such a way that it's hard to determine what actually happened by watching the recording (even though the recording does accurately reflect the session).

[zmb3]

This whole section is mostly prerequisites and not related to enhanced recording. Is the intent that every guide involving SSH nodes should include steps for installing teleport, creating a join token, and joining the cluster? Or can we just document that process in one place and have guides assume you have a node running?

[ptgott]

I wanted to make this more like our Database Access guides (e.g., https://goteleport.com/docs/database-access/guides/mongodb-atlas/) where we include as much information as possible in a single guide so users don't need to break focus to follow the guide (https://goteleport.com/docs/contributing/documentation/style-guide/#how-to-guides).