Add notice to STQ Upload to encourage use of STQ
# Background
In https://gitlab.com/crossref/issues/-/issues/1092 we document a bug impacting who can use STQ Upload. However, as STQ Upload is a little-used service (<50 uses/day) and members can use STQ or the API to match/deposit references, we are considering deprecating it. A recent survey of users indicated STQ meets their needs. Rather than spend the effort to fix this bug, we'll post a notice about potential deprecation and about who can currently use the service.
# Observed behavior
[comment]: # (Please provide as many details as you can about steps to reproduce, operating system, browser, and version used, screenshots, example submission IDs, example XML, example queries, etc)
# Expected behavior
Add this notice:
"We are considering deprecating this service. While we make this evaluation, STQ Upload is only available for users who have previously registered their email addresses with Crossref. Please use [Simple Text Query](https://doi.crossref.org/simpleTextQuery) to match your references."
# How urgent
[comment]: # (There are myriad factors that go into prioritizing and scheduling development work, but any information you can provide to help us understand severity, urgency, relative priority, or deadlines, is much appreciated.)
[comment]: # (No need to update the Definition of ready when filing issues, but feel free to have a go if you're familiar with the territory.)
# Definition of ready
- [x] Product owner: @SaraBowman
- [ ] Tech lead:
- [x] Service:: label applied
- [x] Definition of done updated
- [ ] Acceptance testing plan:
- [ ] Weight applied
[comment]: # (Feel free to leave this as is, or suggest changes. We'll update these during Backlog Refinement, prior to bringing this into a sprint.)
# Definition of done
- [ ] Unit tests identified, implemented, and passing
- [ ] Code reviewed
- [ ] Available for acceptance testing via a staging URL, or otherwise
- [ ] Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed
- [ ] Knowledge base reviewed and updated
- [ ] Public documentation reviewed and updated
- [ ] Acceptance criteria met
- [ ] Add the above text/link to the STQUpload page
- [ ] Acceptance testing passed
# Notes
[comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)
issue