fix(profiles): follow the jobs API

Four POST routes became one collection with the operation in the body, so the
three route pages collapse into one. samples became sample. Creates send an
Idempotency-Key and return a status_url to poll, which the client follows
rather than building the path.

Full rebuild is closed: regenerate_profiles answers 501 not_yet_available and
the docs say so instead of teaching a daily cadence that cannot run.

docs/api-reference/profiles/generate-profiles.mdx

@@ -0,0 +1,5 @@
+---
+title: 'Generate Profiles'
+description: "Start one generation: sample a few entities, build one, or rebuild the project."
+openapi: post /v2/profiles/jobs/
+---

docs/api-reference/profiles/get-profile-job.mdx

@@ -0,0 +1,5 @@
+---
+title: 'Get Generation Job'
+description: "Read the progress of a generation, and whether it finished."
+openapi: get /v2/profiles/jobs/{job_id}/
+---

docs/api-reference/profiles/regenerate-profiles.mdx

@@ -1,5 +0,0 @@
----
-title: 'Regenerate Profiles'
-description: "Rebuild the profile of every entity in the project, applying the current schema to entities that already have one."
-openapi: post /v2/profiles/regenerate/
----

docs/api-reference/profiles/sample-profiles.mdx

@@ -1,5 +0,0 @@
----
-title: 'Sample Profiles'
-description: "Generate profiles for a small set of real entities to evaluate a schema before applying it across the project."
-openapi: post /v2/profiles/samples/
----

docs/api-reference/profiles/trigger-profile.mdx

@@ -1,5 +0,0 @@
----
-title: 'Generate Profile'
-description: "Generate or refresh the profile for a single user or agent immediately, instead of waiting for the message threshold."
-openapi: post /v2/profiles/trigger/
----