Add support for optogenetic FIP sessions and improve file pattern detection

**Description:**

Currently, the FIP metadata mapper only supports one rig configuration and file naming convention. After attempting to apply the existing mapper code to past data, I discovered that ~119 out of 745 sessions use a different rig setup with different naming conventions. After some back and forth with @hagikent, I discovered that this actually the FIP format that is produced by the opto characterization rig. So we need to modify the mapper to handle this also.

The opto rig differs from the configuration expected by the existing mapper as follows:

1. **Different file naming patterns:**
- Standard: `FIP_DataG_*.csv`, `FIP_DataR_*.csv`, `FIP_DataIso_*.csv`
- Optogenetic: `Iso_*.csv`, `Signal_*.csv`, `Stim_*.csv`

2. **Different hardware configuration:**
- Single detector instead of multiple
- Additional stimulation LED (variable wavelength/power)
- Different light source metadata

**Proposed solution:**
- Rename `example_create_session.py` → `create_fip_session.py`
- Create new `create_opto_fip_session.py` with configurable stimulation parameters
- Update file pattern detection to handle both naming conventions
- Rename `pavlovian_behavior/example_create_session.py` → `create_pavlovian_session.py` for consistency

**Acceptance criteria:**
- [ ] Both file naming patterns work automatically
- [ ] Optogenetic script accepts wavelength/power as CLI arguments
- [ ] All existing functionality preserved
- [ ] Scripts renamed for clarity