Introduce trusted root authorities, publishers and untrusted (revoked) certificates store

[kwvg]

Description

Initial designs for main network presumed the usage of an administrative pallet for managing trust-critical operations and intended to embed the root certificate authority within the chain specification. In doing so, it was found that this provided a lack of flexibility (i.e. set the canonical root certificate in stone with future updates being "iterations" rather than replacements) and had a single point of failure (i.e. the sudo pallet has its powers assigned only to one key with no multi-signature functionality)

Therefore, taking inspiration from Certificate Stores, the creation of a key-value database that is modifiable only by a 3/4ths majority of the "foundation pool" (i.e. identities linked with key decision-makers of the organization) would mimic both, a certificate store and a revocation list.