Production-ready policy service

[gkc]

Is your feature request related to a problem? Please describe.

Policy service concept has been proven and a fully functional file-based policy service prototype has been completed but now we need a production-ready policy service.

Describe the solution you'd like

Make a production-ready policy service:

• policy service using atServer for persistence
• policy service using PostgreSQL for persistence
• policy dashboard GUI MVP
• policy dashboard API MVP
• Modify build scripts so that the policy service is included in the release tarball
• Add end-to-end tests which exercise the policy service (one positive, one negative)

[gkc]

Still a bunch more work to do on this

[gkc]

During PR97, split out the core policy framework into its own package, and made it generic - i.e. no hard or soft (semantic) dependency on noports. Refactored noports code accordingly. Added

During PR98, will
. publish core policy package
. ensure noports works with new policy-related requests and responses
. ensure new policy service supports the requests which were supported by the alpha, since we have some alpha policy services in the field
. get noports pull request with all of the new policy stuff reviewed and merged

[XavierChanth]

@gkc it would be useful to have a readonly version of the np_admin dashboard. When we are using a policy engine which is tied into some externally managed source, it would be nice to still use the dashboard for observability and auditing purposes.

[gkc]

No progress in PR100 during which most of my time was spent on this PR and the remainder investigating and/or fixing other bugs

[gkc]

Feature-complete; aiming to get everything published and released this week

• standalone generic at_policy package with documentation and basic code samples (Monday) PR merged: feat: new "at_policy" package for building policy services on atProtocol at_libraries#731
• revised NoPorts policy implementation using the new package, plus backwards compatibility (Thursday)