DAS-2255: Update link pattern in the extract-release-notes file.

[flamingbear]

Description

Quick fix for the release notes extraction script.

I thought the extraction was broken, but it wasn't you can see the release

https://github.com/nasa/harmony-SMAP-L2-gridding-service/releases/tag/0.0.1

That said, the extraction release script was including the markdown reference to the release (even if GitHub ignored it when creating the release). This just fixes that bug.

This is even less important, because that link pattern only matters on the first release, but when I inevitably come and steal this script for the next new service, I'd like it to work.

Jira Issue ID

DAS-2267

Local Test Steps

1. checkout main and run the releast notes script from the root directory:

❯ ./bin/extract-release-notes.sh

You will see that the extracted code includes the link reference at the bottom

### Added

- Initial codebase that transforms SPL2SMP_E granules into NetCDF4-CF grids. [#1](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/1)
- Code and configuration to wrap gridding logic into a Harmony Service [#3](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/3 )
- GitHub actions CI configuration [#4](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/4 )


[v0.0.1]: https://github.com/nasa/harmony-SMAP-L2-gridding-service/releases/tag/0.0.1

Checkout this branch and run it again:

❯ ./bin/extract-release-notes.sh

You should see that the code no longer includes the markdown reference.

### Added

- Initial codebase that transforms SPL2SMP_E granules into NetCDF4-CF grids. [#1](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/1)
- Code and configuration to wrap gridding logic into a Harmony Service [#3](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/3 )
- GitHub actions CI configuration [#4](https://github.com/nasa/harmony-SMAP-L2-gridding-service/pull/4 )

PR Acceptance Checklist

• [N/A] Jira ticket acceptance criteria met.
• [N/A] CHANGELOG.md updated to include high level summary of PR changes.
• [N/A] docker/service_version.txt updated if publishing a release.
• [N/A] Tests added/updated and passing.
• [N/A] Documentation updated (if needed).

[owenlittlejohns]

This is even less important, because that link pattern only matters on the first release, but when I inevitably come and steal this script for the next new service, I'd like it to work.

Ha, yeah, exactly this.