Drop deprecated ci-templates, adopt CI/CD components

Written with the assistance of Claude.

Leaving as draft until the following action items are done

• Figure out what to do about macOS tests that rely on ci-template that doesn't have analogous component as far as I can tell
• Test package component with upload to test.pypi.org
  • upload
  • CI job
• Set up manual SCCB job
  • SCCB ticket successfully created on my own fork at cody.messick/gwcelery#7 by CI job.

Once this is merged, I plan to set up a schedule to run the CI pipeline daily. The test deployment has been changed in this MR such that it won't get automatically triggered by the scheduled pipelines.

A new CI job is included that compares a copy of the SCCB issue template that's been committed to the SCCB issue template in the SCCB repo. This makes it so we don't need to interact with the SCCB repo whenever we want to open a ticket.

The pypi CI Job is now called twine, it comes from the package CI/CD component.

• Note: It appears that the twine job will always automatically trigger on tags. This shouldn't be an issue in general, but librarians that have pypi api access tokens on their personal account need to be careful to never push tags to their personal fork. CC @geoffrey.mo @brandon.piotrzkowski @deep.chatterjee @sushant.sharma-chaudhary

The SCCB CI job is now manually run using a script and and a copy of the issue template from the repo.