Prefer sourcing additional app directory entry metadata from publishing parameters

[apetro]

Whereas up to this point uPortal-home has largely relied upon custom portlet-preferences exposed via ad-hoc hacks to uPortal,

now add support for sourcing that configuration from portlet publishing parameters (which are all exposed in the portlet registry JSON without requiring ad-hoc hacks to uPortal),

so that uPortal adopters can add uPortal-home-supporting metadata to their portlet publications without having to hack uPortal to make these effective.

And then make this the preferred approach, deprecating the hacky support for conveying this stuff via portlet-preferences.

[apetro]

Locally backlogged in MyUW for Scrum purposes as MUMUP-3219.

[ChristianMurphy]

📓 Blocker for widget support in uPortal-Project/uPortal-start#84

[apetro]

These portlet publishing parameters. In what JSON API are they exposed by uPortal? Not seeing them, on messing with uPortal-start locally?

EDIT: cf uportal-dev@ thread.

Publishing parameters are currently included in

/uPortal/api/v4-3/dlm/portletRegistry.json

and

/uPortal/api/v4-3/dlm/layout.json

[ChristianMurphy]

/cc @drewwills @bjagg