Better inclusion of events in documentation and test dApp

[ac10n]

Currently, the documentation, code examples and test dApp are not using events as the primary way of reacting to changes in the wallet.

• Include events in documents, so that people who create new dApps know the recommended way is to use events
• Sample code should include events
• test dApp should react to all events by logging them into the console, or better yet, include a separate div component that displays what event is currently being captured.

relevant slack conversation:
https://ecadlabs.slack.com/archives/CMX5YM1AM/p1697642427609039