nightly: remove stale bf_tree feature from DISKANN_FEATURES

[Copilot]

The nightly clippy-features (macos) job was failing because nightly.yml still listed bf_tree in DISKANN_FEATURES, but no workspace package defines that feature. The diskann-bftree crate is a first-class workspace member and needs no feature gate; ci.yml had already dropped bf_tree but nightly.yml was never updated.

Changes

• .github/workflows/nightly.yml: remove bf_tree, from DISKANN_FEATURES, aligning it with ci.yml.

After the fix, it passes: https://github.com/microsoft/DiskANN/actions/runs/26866739218

[Copilot]

Pull request overview

Removes the stale bf_tree entry from the DISKANN_FEATURES env var in the nightly GitHub Actions workflow so the nightly clippy-features (macos) job no longer references a non-existent workspace feature, aligning nightly.yml with the already-updated ci.yml.

Changes:

• Drop bf_tree from the DISKANN_FEATURES list in .github/workflows/nightly.yml.
• Keep the nightly feature matrix consistent with CI by only listing currently supported feature flags.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.46%. Comparing base (f8bbf3e) to head (4790a6e).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1112   +/-   ##
=======================================
  Coverage   89.46%   89.46%           
=======================================
  Files         482      482           
  Lines       91092    91092           
=======================================
  Hits        81497    81497           
  Misses       9595     9595           

Flag	Coverage Δ
miri	89.46% <ø> (ø)
unittests	89.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.