issues: add pep-723 to issue template

[ianhi]

Adds pep-723 compliant metadata to the placeholder for the reproducer in the bug report

You can see how it will render by making a new issue here: https://github.com/ianhi/git-expt/issues

closes: #2953

[d-v-b]

thoughts on whether the zarr version should point to main branch on github?

[ianhi]

I like that idea. I've pushed a change to do that, as well as moved it from placeholder text to value so that it's copy pastable by the user.

[d-v-b]

do we want to make it uv-specific? I think you can use regular pypi dependency syntax in the pep-723 block

[d-v-b]

e.g.

# /// script
# requires-python = ">=3.11"
# dependencies = [
#     "zarr@git+https://github.com/zarr-developers/zarr-python.git@main",
# ]
# ///

[ianhi]

Good catch. I used the generic form, I also linked to active docs as suggested by the PEP documetn

[d-v-b]

the upstream tests are failing right now because of incompatibility between s3fs and fsspec. I will merge this anyway

[d-v-b]

the upstream tests are failing right now because of incompatibility between s3fs and fsspec. I will merge this anyway

the github UI will not let me merge until the checks pass. I'm trying to sort out the upstream test failures here