Update stripes-docker role in folio-ansible to post UI module descriptors

Made a few modifications:

• Updated "testing" group so that module descriptors are loaded (default was false) to take advantage of new `--strict` flag for package2md.js in stripes-core (https://github.com/folio-org/folio-ansible/commit/6837e0f54d3b8942a6aed68ce608433c8412f9c4).

• Created new variable `stripes_strict_md` (default false) and updated build-module-descriptors.js so that there is an option to create mod descriptors with dependencies from the platform package.json file (https://github.com/folio-org/folio-ansible/commit/45e151f6b1c8728ddaee4bd84df543bbf3047415).

Merged into master of folio-ansible

Work is complete in branch https://folio-org.atlassian.net/browse/FOLIO-636#icft=FOLIO-636 of folio-ansible

The module descriptors generated by package2md.js create ids for the modules that are unfortunately invalid for Okapi – e.g. @folio/users-2.7.1-SNAPSHOT.324. In my testing, Okapi accepts neither the @folio/ prefix nor the -SNAPSHOT.324 suffix. Created and linked issue https://folio-org.atlassian.net/browse/STRPCORE-12#icft=STRPCORE-12.

It's done. The three main UI modules (users, items, scan) all now have an okapiInterfaces section in their package-file declaring their dependencies on back-end interfaces provided via Okapi. (I'll do the same for ui-organization and ui-developer today.) The stripes-core/util/package2md.js script transforms these package files into module descriptors. Wayne will then use these in some way – I don't know the details – to configure the back-end. (It may be as simple as inserting them into Okapi.)