Add release GitHub actions

[klwetstone]

closes #317
closes #389

Add GitHub actions to publish on release

Do not merge - #315 is needed first. After transfer, the repo should automatically have access to the PyPI secrets needed by release.yml

ccds.__version__

Users can now see the version of ccds after importing (ccds.__version__). However, the project name is different than the module name. This means that in version.py, we have to hard code the project name with:

__version__ = importlib_metadata.version("cookiecutter-data-science")

Instead of using:

__version__ = importlib_metadata.version(__name__.split(".", 1)[0])

Using release version as default tag for checkout

Per #389, we wanted a way to allow more stable behavior when someone installs ccds. Currently, any change to the template on the master branch will automatically get propagated when someone runs ccds (unless the person has downloaded the template already and opts to skip that step). As part of this PR, we now default to ccds checking out the tag associated with the installed ccds version.

Users can always get the latest by checking out the master branch (-c master) or updating ccds.

Docs

This PR does not include versioning for docs (eg. with a "Build docs" job). That is tracked separately in #334

[jayqi]

LGTM

[pjbull]

Great! Looking good with one question.

May be nice to also add some instructions on creating a release for maintainers so they know to tag the release in the right way.

[pjbull]

It looks like some places (like the release tags), we use vX.Y.Z and others we use X.Y.Z. We should check if we need the v prefix here or not.

[chrisjkuch]

@pjbull great catch, would have failed as-is without the "v" prefix. I added a RELEASING.md with some instructions, but feel free to tweak or make suggestions.

[r-b-g-b]

Really nice! A couple of wording tweaks using my status as "kind of still figuring out what's going" on to write what made it click for me.

Also maybe unrelated but I notice that

ccds --version

## Cookiecutter 2.6.0 from /home/robert/projects/codepath-data-infrastructure/.venv/lib/python3.13/site-packages (Python 3.13.1 (main, Dec 19 2024, 14:32:25) [Clang 18.1.8 ])

Outputs the cookiecutter version (2.6.0), not the ccds version (2.0.1). May be inert for the time being and if so I can file an issue for another day.

[chrisjkuch]

@r-b-g-b could you take one more look here? Applied your suggestions and added a warning about v2.0.0 per @pjbull, who has otherwise signed off

[r-b-g-b]

One minor tweak, then good to merge -- great work!

[r-b-g-b]

[nit] my brain found it easier to reason about < 2.0.1 than <= 2.0.0 ("if the version is less than 2.0.1, show the deprecation warning")

Then tweaked the wording a bit -- still correct?

Suggested change

	if version <= "2.0.0":
	warnings.warn(
	"It looks like you're using a version of CCDS that "
	"always uses the latest template. For more stable behavior, "
	"update to a newer version of CCDS.",
	DeprecationWarning,
	)
	if version < "2.0.1":
	warnings.warn(
	"It looks like you're using a version of CCDS that "
	"defaults to using the latest template. For more stable behavior, "
	"update to CCDS version 2.0.1 or later. To upgrade to the latest "
	"version, run 'pip install -U cookiecutter-data-science'",
	DeprecationWarning,
	)

[pjbull]

Would be good to tell people how to upgrade (e.g., pip install -U cookiecutter-data-science)

[r-b-g-b]

Good call -- updated suggestion.