enforceBytecodeVersion: exclude is broken without include

### Affected version

3.6.3

### Bug description

The new rule is broken in respect of being "true drop in". If there are excludes but no includes, it totally messes up filtering.

Workaround: if you need exclude, you must set also include, at least for `*:*` (all).
Example: https://github.com/maveniverse/toolbox/pull/401/changes

Start at the enforceBytecodeVersion rule and reproduce filtering with excludes configured but no includes, then compare it with the documented *:* workaround and the linked pull request changes. Done means excludes work correctly without requiring an include pattern, with regression coverage for the no-include case.

Written by the indexing model from the issue text.