Update API endpoint for profiling setup commands

[inge4pres]

Paired with elastic/kibana#234065, adjust the documentation for the new public API to setup Profiling in 9.2+

[github-actions]

🔍 Preview links for changed docs

• solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md

[florent-leborgne]

Hi @inge4pres. The change itself LGTM, but these docs must also stay accurate for 9.0 and 9.1 users.

I'd propose to use tabs to distinguish between both versions of the path (one for 9.0+9.1, the other for 9.2 and beyond) This could look like this:

To configure data ingestion from the console, go to **Dev Tools** in the navigation menu and run the following command:

::::{tab-set}
:group: versions

:::{tab-item} 9.2+
:sync: 9.2
{applies_to}`stack: ga 9.2`

```console
POST kbn:/api/profiling/setup/es_resources
{}
```
:::

:::{tab-item} 9.0 to 9.1
:sync: 9.0
{applies_to}`stack: ga 9.0`

```console
POST kbn:/internal/profiling/setup/es_resources
{}
```
:::

::::


To configure data ingestion programmatically using a standalone HTTP client (e.g., `curl`), run the following command:

::::{tab-set}
:group: versions

:::{tab-item} 9.2+
:sync: 9.2
{applies_to}`stack: ga 9.2`

```console
curl -u elastic:<PASSWORD> -H "kbn-xsrf: true" -H "Content-Type: application/json" \
    --data "{}" "https://<kibana-host>:<kibana-port>/api/profiling/setup/es_resources"
```
:::

:::{tab-item} 9.0 to 9.1
:sync: 9.0
{applies_to}`stack: ga 9.0`

```console
curl -u elastic:<PASSWORD> -H "kbn-xsrf: true" -H "Content-Type: application/json" \
    --data "{}" "https://<kibana-host>:<kibana-port>/internal/profiling/setup/es_resources"
```
:::

::::

And will look like this in the docs:

[inge4pres]

I'd propose to use tabs to distinguish between both versions of the path

Thanks for the suggestion @florent-leborgne it's great 🙏🏼
There's a caveat though: 9.0 and 9.1 cannot work with the internal endpoint - Kibana blocks it.
There is an unfortunate series of events that brought us here, but basically programmatic setup for Universal Profiling as documented only works for 9.2+ with the fix just merged in Kibana.

What's the best way to express this?
Should we add a section about this in the known issues?

[florent-leborgne]

Ah, then I think we're in a much simpler case, you can forget about my initial suggestion and instead add the following the line right after ### Programmatic configuration [profiling-configure-data-ingestion-programmatic]:

```{applies_to}
stack: ga 9.2
```

This will add a badge to the section indicating that what's described there is only possible from 9.2.

[inge4pres]

add the following the line right after ### Programmatic configuration [profiling-configure-data-ingestion-programmatic]

trying, thanks 🙏🏼

[inge4pres]

trying, thanks 🙏🏼

Apparently the commit I added broke CI? @florent-leborgne did I mess it up?

[florent-leborgne]

That's the other way around, this should make the CI happier :)

[inge4pres]

That's the other way around

Thanks 🙏🏼

[florent-leborgne]

Perfect! Thank you @inge4pres!!