Update acts-as-taggable-on to 5.0
What does this MR do?
Update acts-as-taggable-on dependency to 5.0. Only breaking changes is dropping support for older ruby and activesupport versions, so it does not affect us.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Debian already has 5.0 and it would help in packaging to have dependencies in sync.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-qamanual pipeline job)