As a node operator, I want actionable, user-friendly error messages for registry schema failures

[tloubrieu-jpl]

We can think of 2 steps in the development:

1. improve error message, e.g. describing where to download and the command line to launch to update the schema
2. prepare a repository/database of the LDDs and "automate" the download and update of the schema.

Acceptance criteria

When LDD schema required is when metadata is loaded with registry-mgr but not available in the registry (e.g. metadata using orex namespace).
Then: the error message contains a pointer to the online documentation which helps to solve the error

[tloubrieu-jpl]

@tdddblog @jordanpadams For step 1 I just had an example of user friendly message for pyproj library:

lon, lat = pyproj.transform(fromproj, toproj, x, y)
<input>:1: DeprecationWarning: This function is deprecated. See: https://pyproj4.github.io/pyproj/stable/gotchas.html#upgrading-to-pyproj-2-from-pyproj-1

We could have a link to our mvn site published on github, to the specific page, section which details how to add a new LDD.

[jordanpadams]

already within past merged PR

[jordanpadams]

updated error message:

Updating schema with fields from C:\tmp\harvest\out\fields.txt
[ERROR] Could not find datatype for field 'abcd123'.
See 'https://nasa-pds.github.io/pds-registry-app/operate/common-ops.html#Load' for more information.