cuxfilter: stop development and packaging publishing

[jameslamb]

Description

26.06 will be the last release of cuxfilter, see rapidsai/docs#786

This tracks the work of tearing down references, configuration, etc.

Benefits of this work

Reduces maintenance burden and complexity.

Acceptance Criteria

• 0 lingering unnecessary references to cuxfilter in 26.08 and beyond
• rapids-metadata accurately reflects the state of the 26.06 and 26.08 releases

Approach

This list mostly based on a GitHub search of the rapidsai org (link)

• put up an RSN announcing the plan to remove cuxfilter (Sunsetting cuxfilter after RAPIDS Release v26.06 docs#786)
• move to "Inactive Projects" section of https://docs.rapids.ai/api/
• remove from RAPIDS build infrastructure
  • devcontainers (N/A - no devcontainers)
  • integration - rapids metapackage (remove cuxfilter integration#851)
  • rapids-metadata (drop cuxfilter, update all pre-commit hooks rapids-metadata#78)
  • release-scripts (https://github.com/rapidsai/release-scripts/pull/91)
  • workflows (remove cuxfilter workflows#120)
• other miscellaneous references:
  • deployment docs (remove cuxfilter references deployment#707)
  • docker README (remove cuxfilter references docker#888)
  • rapidsai/cugraph update-version.sh and notebooks (put up an issue, cuGraph maintainers can do this at whatever priority they want: [DOC]: remove or update ForceAtlas2 notebook cugraph#5550)
• Mark the RSN as completed
• remove / mark broken nightly packages (https://github.com/rapidsai/ops/issues/4664)
• archive the repo (once we're far enough from 26.06 that a hotfix is unlikely)
  • put up a notice on main pointing to the RSN (update development status, remove branch CI cuxfilter#793)
  • archive the repo
  • remove from CI allowlist

Notes

based on format from #220