The "more options" modal for filter values in the search filters pane
incorrectly made the assumption that all searchable filters were based
on MPTT paths and built a regexp accordingly.

That is not the case: in our own sandbox environment, persons are not
using those paths and the "more options" for persons modal is broken.
We can simplify the regexp to make it work with every filter.

Bumps [mixin-deep](https://github.com/jonschlinkert/mixin-deep)
from 1.3.1 to 1.3.2.
- [Release notes](https://github.com/jonschlinkert/mixin-deep/releases)
- [Commits](jonschlinkert/mixin-deep@1.3.1...1.3.2)

Signed-off-by: dependabot[bot] <[email protected]>

The "More options" modal for filter values was making request to the
server as soon as the user started to type, and immediately showed a
cryptic error message as it received an error for the server, because
textual search only works in our API endpoints with 3 characters or more.

Stop sending useless API requests when users input 1 or 2 characters and
show a helpful message in the modal instead.

We're using demo-content to showcase richie's feature set as best
we can. In order to make a better demo for the "More options" modal
on filters, and for course pagination, we're increasing the number
or courses & organizations included in the demo site by default.

The string shown in the blogpost detail template when a blogpost
does not have an author - "No author yet." - should not have a
period at the end as it is displayed between two dashes.

Just remove the period from the string in the template.

Our pagination as implemented in course search had two flaws:
- low contrast difference between the currently active page button and
  other pages;
- small clickable zone, only clicks on the page number itself triggered a
  page change, not clicks on the button itself.

We made the clickable area encompass the whole page button, and used a
reverse color scheme for the active page to make it more obvious for all
users (and avoid a WCAG non-conformity for low contrast).

Regenerate the lockfile to ensure only versions > 2.0.1 (safe versions)
of the `set-value` npm package are used.

Visible pagination does not contain a lot of strings, but we have
a few more strings for accessibility helpers that provide context
along with the page numbers.

We previously attempted to do this "smartly" through the HTML
structure of our interpolated strings. This is not ideal as it works
for english and some other languages, but fails for other languages
with a different grammar.

Also, we forgot a bunch of strings, which resulted in hardcoded
english in our template.

Pull and commit latest versions of the translations from our
localization management tool.

Fixed

- Fix "More options" modal for searchable filter values not based on MPTT
  paths (eg. "Person" in the sandbox environment).
- Improve pagination UX by increasing contrast between the active page number
  and others, and making button clickable areas larger.
- Stop making failed API requests and instead show a helpful error message
  in the "More options" modal for filter values when the user inputs their
  first 1 or 2 characters.
- Improve pagination strings for localization.

Security

- Update the mixin-deep and set-value packages to safe versions.