fix: removed prohibitive over-filtering of contract messages

Nested contract-contract calls, e.g. an Execution message on one contract calling the instantiation of another, being obstructed by over-filtering of handler triggers.
- In this example, the instantiation message would not be indexed, as it was called as part of an Execution message. With the previous heavy-handed message filtering, all instantiation calls required the event of type instantiation as well as the message typeUrlto be that of an instantiation.
Schema changed to reflect instantiateMsg optional properties, admin & label.
Removed leftover prints
Refactored handler config into module categories
Added genesis processor config to testing docker-compose.yml

Code Review Checklist (to be filled out by reviewer)

[ ] Description accurately reflects what changes are being made.
[ ] Either the PR references an issue (via the "Development" combobox) or the description explains the need for the changes.
[ ] The PR appropriately sized.
[ ] The PR contains an idempotent DB migration.
[ ] I have verified the correctness of the DB migration using relevant data (e.g. test-generated data).
[ ] New code has enough tests.
[ ] New code has enough documentation to answer "how do I use it?" and "what does it do?".
[ ] Existing documentation is up-to-date, if impacted.