Improved Debugger support - do not require to recreate breakpoints

Currently new file will be created for hot-reloaded code and breakpoints can be added there.

Alternatively in IDE wide function-breakpoint can be set referencing patched class name ChangedClass*__Patched_*

This works but is rather bad user experience.

[ ] Investigate if existing Rider / VS integration packages can be patched by Harmony in a way that'd help improve workflow
[ ] IDE plugin that allows to move existing breakpoints (big issue here is need to install additional IDE plugin)
[ ] other approach? potentially if breakpoints can be read from Unity side maybe adding Debugger.Break in those lines would help?)

Investigate the existing Rider/Visual Studio integration packages and how Harmony could affect them, then compare the proposed IDE plugin and Unity-side Debugger.Break approaches. The issue does not name files or tests, and work is complete only when existing breakpoints can be retained or moved without the current patched-class workflow.

Vom Indexierungsmodell aus dem Issue-Text verfasst.