fix: don't publish tags greater than 30 chars

[vkWeb]

Summary

Description of the change(s) you made

Tags greater than 30 characters won't get published after we merge this PR.

References

Closes #3296.

---

Contributor's Checklist

PR process:

• If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
• If this includes an internal dependency change, a link to the diff is provided
• The docs label has been added if this introduces a change that needs to be updated in the user docs?
• If any Python requirements have changed, the updated requirements.txt files also included in this PR
• Opportunities for using Google Analytics here are noted
• Migrations are safe for a large db

Studio-specifc:

• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
• All UI components are LTR and RTL compliant
• Views are organized into pages, components, and layouts directories as described in the docs
• Users' storage used is recalculated properly on any changes to main tree files
• If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

• Code is clean and well-commented
• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Any new interactions have been added to the QA Sheet
• Critical and brittle code paths are covered by unit tests

---

Reviewer's Checklist

This section is for reviewers to fill out.

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[vkWeb]

@rtibbles merging #3311 will resolve the CI error we have here.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[bjester]

I left a note regarding the changes to the ricecooker API. Could you also add some validation to the frontend API? It should be straightforward to add some validation logic to the serializer or serializer field TagField.

The other last remaining piece is what to do with channels that currently have this issue, but that can be completed in a separate PR

[bjester]

@vkWeb Good thinking on updating the max length on the ContentTag.tag_name, but I don't think we'll be able to change that just yet.

The test failure is due to a migrations check which ensures that all necessary model changes are reflected in the migration files, and that model field change requires a new Django migration. The problem, though, is that if we deploy that migration to the production database which already had tags of >= 30 chars, it will likely fail.