RUM Auto-instrumentation updates

[rtrieu]

What does this PR do? What is the motivation?

Per discussion with @sarjyusuf, this primarily contains the following updates:

• Added a card layout partial to the auto-instrumentation landing page
• Created a page for each auto-instrumentation server (added multi-code lang functionality)
• Added more use case info about auto vs custom instrumentation to the browser setup overview page (removed multi-code lang functionality)
• Updated language for all preview tags that mentioned auto-instrumentation

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

To be reviewed by RUM Eng before merging.

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server/
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server/apache
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server/ibm
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server/nginx
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server/windows_iis

Removed or renamed files (these should redirect)

• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/server

Modified Files

• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/browser/setup/client
• https://docs-staging.datadoghq.com/rtrieu/auto-instrumentation-updates/real_user_monitoring/guide/best-practices-for-rum-sampling

[pablomartinezbernardo]

How is a customer supposed to navigate to this section? Given the path it looks to me like it is supposed to be visible when clicking here

auto-instrumentation-updates/real_user_monitoring/browser/setup

But instead on that left menu, or the breadcrumbs, the content for "real_user_monitoring/browser/setup/client" is shown instead. It might just be me misunderstanding how navigation is supposed to happen, though (If so, can you link to the page here? 🙇 ).

[pablomartinezbernardo]

(Comment applies to all servers)

The phrasing we had before (This instrumentation method does not support any advanced RUM configurations. However, allowedTracingUrls and excludedActivityUrls are supported) didn't imply allowedTracingUrls and excludedActivityUrls are advanced RUM configurations, while now I think it does. They are not mentioned in the advanced RUM configurations page, so that might be confusing.

[dmehala]

I am no native english speaker but the "however" in the original wording seems to indicate allowedTracingUrls and excludedActivityUrls are advanced configuration. I am also non RUM expert, IIRC advanced configuration are configurations supporting arrays and functions, these two are compatible with arrays and functions. Summoning @allspain for clarification.

[pablomartinezbernardo]

Moving Damien's comment into the PR comments: this is not the appropriate logo for IBM HTTP Server