Consider merging with scientific-python template

In May ~2024~ 2023, NSLS-II and scikit-hep merged their templates and associated development guides into one [template](https://github.com/scientific-python/cookie) and [guide](https://learn.scientific-python.org/development/), under the `scientific-python` org. We have seen advantages in maintenance: with shared effort, the shared template is staying better up to date. Our opinions and use cases are not _perfectly_ aligned, but we have been able to find rough consensus on technology choices, and so far we find the benefits of sharing to be higher than the costs.

Let's explore whether it would make sense to merge the DLS/Bluesky copier template into this. Initial questions:

- What technology/layout choices differ between them?
- What would it take to provide facility-specific defaults during set up, so that a new user can mostly just press `` and get the appropriate license file and other facility-local settings? Even if this required an enhancement to copier itself, that could be doable.

Confronta il template copier di DLS/Bluesky con il template scientific-python collegato e la guida allo sviluppo, concentrandoti sulle differenze tecnologiche e di layout. Indaga quindi su come fornire durante la configurazione i valori predefiniti specifici della struttura, i file di licenza e altre impostazioni locali, verificando anche se copier necessiti di un miglioramento. Il lavoro si considera concluso quando viene prodotto un piano di fusione sostenuto dal consenso oppure viene documentato il motivo per cui i template dovrebbero rimanere separati.

Scritto dal modello di indicizzazione a partire dal testo della issue.