Summary

Closes #2361

** note this MR includes the new installer changes, wait for that before merge **

Added in a check for whether the matching tag is located in a URL.

Steps to Test

This one is a bit more "get in there and try your best to break it" in terms of testing, but that said, to get a foot in the door:

1. Go on the site, make a post with 5 hashtags; try to trip the Regex up and make some invalid tags to see how it responds to the max count.
2. Try a URL with a hashtag in.
3. Check the hashtags links go through to the correct place.
4. Try to use the hashtag selector to bypass the limit
5. Ensure when you add a tag it shows up in the selector

Estimated Regression Scope

This change could affect the poster in different environments, it could perhaps trigger something that should still not be a hashtag as a hashtag

added scoped label

added 12 commits

• 0e69ebb8...745769a5 - 11 commits from branch master
• 547ff898 - Merge branch 'master' of gitlab.com:minds/front into fix/url-hashtag-count

Compare with previous version

Works pretty good for most of the cases I tried, but it seems that it parses the first half of a word that starts with the pound sign as a hashtag as well. Check the image below:

added scoped label

assigned to @benhayward.ben

added 5 commits

• 547ff898...28b1e2b3 - 4 commits from branch master
• 6782df1a - Merge branch 'master' of gitlab.com:minds/front into fix/url-hashtag-count

Compare with previous version

No worries. Very weird though because it's not happening locally, but definitely is on the sandbox.