Mark aube lockfiles as generated

[risu729]

Recognize aube-lock.yaml as generated so it is excluded from language statistics and collapsed in diffs, like other supported package-manager lockfiles.

Description

aube generates aube-lock.yaml as its default dependency lockfile. Its lockfile documentation describes how install, add, remove, update, dedupe, and import write it; the writer implementation serializes the resolved dependency graph.

The rule matches the exact basename at the repository root or in a subdirectory. Tests cover those paths, detection without loading file contents, and similarly named files that must remain unmarked. No language definitions or sample files are added.

Public usage: GitHub code search excluding forks, with examples in coder/agent-tty, tuist/tuist, and tstyche/tstyche.

Validation: bundle exec rake test on Ruby 4.0.7 with a case-sensitive APFS volume: 2,049 tests, 41,107 assertions, no failures, errors, or skips.

Checklist:

• I am adding new or changing current functionality
  • I have added or updated the tests for the new or changed functionality.

[risu729]

Sorry for opening this PR before adequately checking adoption. I haven't established sufficient widespread usage of aube-lock.yaml, so I'm withdrawing it.

The contribution guidelines document a minimum of 200 indexed files for filenames expected once per repository, or 2,000 for those expected more often, excluding forks and with a reasonable distribution across owners and repositories. I should not have assumed that the generated-file functionality checklist established an exemption from demonstrating common usage.

Current browser searches report roughly 107–116 matching files, while the legacy API reports a higher, inconsistent count. These results do not give me a reliable basis to claim the documented usage benchmark is met. Apologies for the premature submission.