STRWEB-143: Add subscribesTo field to module metadata.

[Dmytro-Melnyshyn]

Purpose

Add subscribesTo to stripes.metadata to read the list of apps requiring a servicepoint from stripes, instead of using a hard-coded list.
Apps that rely on servicepoints should have "subscribesTo": ["servicepoints"] in package.json::stripes:

"stripes": {
  "subscribesTo": ["servicepoints"]
}

This will display the following modal if a servicepoint is missing:

Issues

https://folio-org.atlassian.net/browse/STRWEB-143

[github-actions]

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit d79551c. ± Comparison against base commit 0ef6273.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zburke]

LGTM

Which do you think is better:

• copy only named properties of stripes into metadata, as we do here?
• copy all stripes properties into metadata, naming a few properties to exclude (e.g. permissions and translations), so we don't have to update stripes-webpack just because we want to add a new property?

You could convince me either way.

[Dmytro-Melnyshyn]

@zburke Metadata is a public API - new properties should be intentional, reviewed, and documented at least in a PR. Otherwise, every UI module can add whatever they deem necessary, which could lead to a mess.