Comet Targets produce undesireable directory layout for dataproducts

[talister]

Describe the bug
Since the slash in non-short period comet names e.g. "C/2021 G2 (ATLAS)" or "P/2024 O2" is preserved when creating a Target from the JPL Harvester, successful observations for these Targets contain an additional (unwanted) level of directory depth e.g.

(fomo311_venv) [tlister@tlister-thinkmate src]$ tree
.
├── data
│   └── ATLAS (C
│       └── 2021 G2)
│           └── LCO
│               ├── cpt1m012-fa06-20250213-0429-e00.fits.fz
│               ├── cpt1m012-fa06-20250213-0429-e00_tb.jpg
│               ├── cpt1m012-fa06-20250213-0429-e91.fits.fz
│               ├── cpt1m012-fa06-20250213-0429-e91_tb.jpg
│               ├── cpt1m012-fa06-20250213-0432-e00.fits.fz
│               ├── cpt1m012-fa06-20250213-0432-e00_tb.jpg
│               ├── cpt1m012-fa06-20250213-0432-e91.fits.fz
│               └── cpt1m012-fa06-20250213-0432-e91_tb.jpg

To Reproduce
Steps to reproduce the behavior:

1. Obtain observational data on a comet target
2. Save DataProducts
3. Run e.g. tree on the directory of stored data
4. See error

Expected behavior
Comet names should be sanitized to remove special characters, particularly the path separator, when they are being used to create directories for storing data

Desktop (please complete the following information):

• OS: Rocky Linux 9.5
• Browser: N/A
• Version: 2.23.1
• Python Version: 3.11.9