rewrite manifest module registry

[tabcat]

The registry contains components. The components are referenced by a key in a database manifest. If the components referenced by the manifest are registered, the database can be opened and SEC is ensured.

The plan is to use something like protocol ids for registration and resolution so that components can be upgraded since versioning is included. Also the prefix will make sure that components of different categories are not mixed up, e.g. a store component is not registered as an access component.

[tabcat]

from looking at https://github.com/libp2p/js-libp2p/blob/master/src/ping/index.ts and https://github.com/libp2p/js-libp2p/blob/master/src/identify/index.ts it looks like the structure of a protocol id is /<protocol prefix>/<protocol name>/<protocol version>. will use this same structure for manifest components and possibly other places like the manifest itself in a version field.

[tabcat]

since my plan is to have the protocol prefix include the type of component, e.g. one of store, access, entry, identity, it might not be necessary to have a unique registry for each type. will see what route looks best.

[tabcat]

Going to be keeping a register for each component after all so typescript can say whether one fits that register or not.