Final Merge of BinjaExportTox64dbg in Binary Ninja's Plugin Manager

[utkonos]

@psifertex We have decided to merge the capabilities of BinjaExportTox64dbg and this plugin and the maintainer of that one has joined this project. The other plugin will be redundant once the merge is done and released. What would you suggest as the best way to handle this from the plugin manager's perspective? Should there be a stub plugin for BinjaExportTox64dbg that points users to this plugin? Should that plugin just be deleted? Or is there another more elegant suggestion you may have?

This issue is for the final dispensation and appropriate handling of the other plugin.

This was all discussed in the following issue in the other repo:
moval0x1/BinjaExportTox64dbg#1

[psifertex]

Unfortunately we don't have a great mechanism in the current plugin manager for gracefully migrating away from the previous plugin. It's something we've thought about but it happens rarely enough that it hasn't been a high enough priority to implement yet.

I leave it up to you to decide whether to leave a stub or to have us simply remove it, either is a fine outcome from my perspective.

It's great to see the collaboration either way!

[utkonos]

@psifertex Ok, perhaps we phase it? Leave a stub with a message pointing to the one plugin, then after some period of time, or maybe a release or two of Binja, it gets nuked?

When the merged version is ready and released, we could add a click though popup to the other plugin at first. Something nobody could miss. Along with a message on the README about using this plugin. Then after some period of time, just nuke that plugin from the manager.