Make include_tags & exclude_tags params more robust

[Oaphi]

closes #2010

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.73%. Comparing base (4deef91) to head (60bfc1f).
⚠️ Report is 15 commits behind head on develop.

Additional details and impacted files

Components	Coverage Δ
controllers	75.82% <ø> (-0.04%)	⬇️
helpers	85.09% <100.00%> (+0.02%)	⬆️
jobs	66.88% <ø> (ø)
models	93.01% <ø> (ø)
tasks	61.11% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cellio]

A valid filter URL is like this:

http://localhost:3000/categories/1?sort=&predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags%5B%5D=8

I hand-edited that make include_tags have an invalid value, like this:

http://localhost:3000/categories/1?sort=&predefined_filter=&min_score=&max_score=&min_answers=&max_answers=&status=any&include_tags=%5B8%5D

On develop that causes a server error; on this branch it does not.

I don't know if we care, but with the invalid URL, it renders the category page as expected, but it shows with a filter applied but the tag is missing:

If there is no on-site way to create that malformed URL then I don't care, but I mention it in case there are other implications.