feat: make catalog_path configurable in plot_catalog function for 4FDGL Fermi catalog

[azegarelli]

This PR introduces an optional catalog_path argument in the plot_catalog function.

• If not provided, the function defaults to the existing constant CATALOG_PATH.
• If provided, users can specify any Fermi 4FDGL catalog file https://fermi.gsfc.nasa.gov/ssc/data/access/lat/14yr_catalog/ to be plotted.

---

This change is particularly crucial for Docker containers that automatically process track alerts:

• Containers can now access and use catalogs directly, without depending on the static CATALOG_PATH.
• Without this option, it is impossible for containerized scripts to use plot_catalog flexibly (e.g. for plotting 4FGL). Indeed, up to now we’ve had to run this functionality manually in our own Condor spaces. With the proposed change, Docker containers will be able to automatically generate plots with Fermi gamma-ray sources overplotted on the best-fit direction and map.

---

Benefits

• Increases flexibility in catalog version usage
• Simplifies integration with automated pipelines and containerized workflows
• Maintains backward compatibility (default path still works)

[G-Sommani]

@ric-evans, do you know why so many checks are failing? For sure it is not because of this modification.

[azegarelli]

@ric-evans, do you know why so many checks are failing? For sure it is not because of this modification.

thanks @G-Sommani for pointing this out.
indeed, these failures seem to be related to the latest Dependabot pull requests.

[ric-evans]

back from vacation -- I'll fix these failures in another branch

[azegarelli]

@tianluyuan I realized I need to update also https://github.com/icecube/skyreader/blob/main/skyreader/plot/plot.py to allow the user to properly pass the catalogh path variable.
I'm restoring the branch

[azegarelli]

Now the branch contains all the changes I need.
Please don’t remove the branch, even after it’s merged. Whether I realize that something else needs to be modified (though I don’t think so), I can continue making changes in the same branch. Thanks :)

[ric-evans]

Now the branch contains all the changes I need. Please don’t remove the branch, even after it’s merged. Whether I realize that something else needs to be modified (though I don’t think so), I can continue making changes in the same branch. Thanks :)

The branch is auto-deleted when the PR merges. You would need to create a new branch from main, then make a new PR; ie: feature/optional-catalog-path-2

[azegarelli]

Now the branch contains all the changes I need. Please don’t remove the branch, even after it’s merged. Whether I realize that something else needs to be modified (though I don’t think so), I can continue making changes in the same branch. Thanks :)

The branch is auto-deleted when the PR merges. You would need to create a new branch from main, then make a new PR; ie: feature/optional-catalog-path-2

ok thanks :) I didn't know