ops_repo plugin bitops folder

**Is your feature request related to a problem? Please describe.**
Expanding on functionality from `BitOps V1`, the ops_repo level bitops files and folders should be consolidated into a single place for better management and organization.

**Describe the solution you'd like**
As I implement the hooks, I’m becoming hesitant to reimplement our current pattern;
```
ops_repo/
env/
plugin/
plugin.related.files
bitops.config.yaml
bitops.before-hooks.d
bitops.after-hooks.d
```
I’d like to propose that we move these files into a bitops folder which will consolidate the bitops related files into a single location, reduce the bloat bitops imposes on plugins specific configuration files and (imo) just look cleaner
```
ops_repo/
env/
plugin/
plugin.related.files
bitops/
bitops.config.yaml
bitops.before-hook.d
bitops.after-hook.d
```
**Describe alternatives you've considered**
We are implementing the V1 Bitops ops_repo files and folder pattern for the initial V2 launch. However, in the future I'd like to make this a "legacy" option and expand the folders to be more customizable and organized.

Start by inspecting the current ops_repo/env/plugin layout and the BitOps V1 files, especially bitops.config.yaml and the before- and after-hook directories. Trace how these paths are discovered and used. Done means the proposed ops_repo/env/plugin/bitops structure is supported while the existing pattern is treated as a legacy option, with the organization and migration behavior documented.

Written by the indexing model from the issue text.