docs: update buckets recreation procedure

[joanagmaia]

This pull request updates the documentation for the bucketing architecture bootstrap procedure in services/libs/tinybird/bucketing-architecture.md. The main focus is to clarify and make the snapshotting process safer by providing a more detailed, step-by-step guide and explaining the importance of pausing enrichment during the process.

Improvements to the snapshot bootstrap procedure:

• Expanded the bootstrap procedure steps to clarify that snapshot pipes use append mode and to provide a safer, more granular process for recreating buckets, including pausing enrichment, truncating datasources, running snapshots, and resuming enrichment.
• Added an explanation for why the enrichment copy pipe should be paused before truncating datasources, highlighting the risk of producing empty or partial results if not paused.

---

Note

Low Risk
Low risk documentation-only change; no runtime or data-path code is modified.

Overview
Updates services/libs/tinybird/bucketing-architecture.md to clarify that snapshot pipes run in append mode and therefore require an explicit rebuild workflow.

Replaces the previous “run all snapshots” guidance with a safer per-bucket sequence: pause the corresponding enrichment copy pipe, truncate the raw bucket datasource, run the snapshot pipe, verify distribution, then resume enrichment, with an added note explaining why pausing prevents empty/partial enrichment results.

^{Written by Cursor Bugbot for commit e25daf1. This will update automatically on new commits. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.