Incorrect BIDS example

on https://docs.emberarchive.org/user-guide/data-standardization/ has

```
my_dataset/
├── dataset_description.json
├── participants.tsv
├── participants.json
├── sub-01/
│ ├── ses-01/
│ │ ├── ieeg/
│ │ │ ├── sub-01_ses-01_task-rest_ieeg.nwb
│ │ │ ├── sub-01_ses-01_task-rest_ieeg.json
│ │ │ ├── sub-01_ses-01_task-rest_channels.tsv
│ │ │ ├── sub-01_ses-01_task-rest_electrodes.tsv
│ │ │ └── sub-01_ses-01_task-rest_events.tsv
│ │ │
│ │ ├── beh/
│ │ │ ├── sub-01_ses-01_task-rest_beh.tsv
│ │ │ └── sub-01_ses-01_task-rest_beh.json
│ │ │
│ │ ├── video/
│ │ │ ├── sub-01_ses-01_task-rest_video.mp4
│ │ │ └── sub-01_ses-01_task-rest_video.json
│ │ │
│ │ └── audio/
│ │ ├── sub-01_ses-01_task-rest_audio.wav
│ │ └── sub-01_ses-01_task-rest_audio.json
```

which I think flawed on a number of levels
- `beh/` typically is for "behavior only", otherwise all relevant info during experiment like `ieeg` would just go into that folder.
- audio/video folders -- I guess, since that is where the catch here since audio/video would go depending on their "purpose",
the last ones likely to follow [BEP047](https://bids.neuroimaging.io/extensions/beps/bep_047.html) to capture behavior. And that is where it would then go under `beh/` following https://bids-specification--2231.org.readthedocs.build/en/2231/modality-specific-files/behavioral-experiments.html . Note that likely you might just have here `_audiovideo.mp4`. If they are for different devices , likely worth adding `_recording-` to clearly disambiguate "what is different" between those two

Overall, for such an example I would recommend to

- prepare PR against https://github.com/bids-standard/bids-examples/ depicting target scenario (if not there already?! check PRs for BEPs there)
- use bids-validator on it to validate that it is legit. Note that if uses a BEP -- should validate using its schema (in PR for bids-examples can point to which BEP PR to use to validate). If multiple -- that is where we might want to establish and track combination of PRs.