EPIC: Feature Parity with Theia Extension

**Description**

- Improve handling of debug session lifecycle: https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/6
- [x] Track capabilities of created sessions
- [x] Set context based on active session
- [x] Check capabilities of active session
- [ ] Handle capability events?
- [ ] #97
- Improve View
- [x] Use monospace in view. https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/8
- [ ] Implement change marking.
- [x] Copy paste should produce a grid, not a vertical list. (Fixed by #57)
> Can't use VSCode Grid components for this, [at least for now](https://github.com/microsoft/vscode-webview-ui-toolkit/issues/374).
- [x] #123
- [x] Implement hover (#66)
- [x] #24
- [x] #11
- [x] Option to disable dynamicity in-view, maybe also via preference
- [ ] Highlighting of changes
- [x] Implement Configuration Widget: https://github.com/eclipse-cdt-cloud/vscode-memory-inspector/issues/7
- [ ] Implement Diffing #9
- [ ] Implement Memory Write UI #10
- Implement Memory Search UI
- [x] #12
- [ ] Option for full resolution (incl. sizes) vs. marking start
- [x] #13
- [ ] Implement Data Breakpoint (Watchpoint) UI
- Implement Register View?
- [ ] Register + memory linkage to show registers pointing at memory regions?
> Since registers are supposed to be handled in the variables request, maybe there's no need for a separate view in the Memory Inspector? Are there areas where we can go beyond the presentation in the Variables Widget?
- Implement Contribution System?
> Idea here would be to identify behavior that differs among adapters and let plugins that contribute debuggers also modify Memory Inspector behavior. Some areas that might differ: resolving variable sizes or internal structure, memory searchability, variable reference syntax (though the memory reference field of the DAP mostly covers that).