chore(ci): run expensive Component Features check weekly

[pront]

Summary

The component features check is one of our most resource-intensive CI jobs:

• Runs 200+ individual feature builds (one for each component feature in isolation)
• Takes 1+ hours to complete
• Typically fails only after a new component was introduced (can run it on demand before merging those)
• Running 5x per week on schedule is excessive for a check that validates feature gate correctness

Pros:

• Significant cost savings - 80% reduction in scheduled runs (5/week → 1/week)
• Still catches issues - weekly run ensures feature gate bugs don't accumulate
• On-demand available - can still trigger manually or via PR review when needed

Cons:

• Longer feedback loop - feature gate bugs might not be caught until the following Monday
• One run can expose more than one issue, slightly harder to fix. Although this is possible today e.g. we merge two PRs and both introduce a new issue.
• Monday disruption - failures will require attention early in the week

Future work:

• Use cargo hack - feat(ci): use cargo hack to perform single feature compilation checks #23961

Vector configuration

How did you test this PR?

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.