Improve automatic symbol pairing for functions with compiler-generated names

[LagoLunatic]

A couple of improvements for automatically pairing up functions with weird symbol names. MWCC can output symbols in a different order from their actual address order, so they're now internally sorted to handle the case of a single TU having multiple functions with different discriminators so they don't get swapped during pairing.

Before:

After:

And discriminators in the middle of anonymous class names like __dt__Q29dCamera_c23@class$3665d_camera_cppFv are now also ignored, in addition to the ones at the end of the symbol which were already ignored.

Fixes #266

[LagoLunatic]

Added another fix, this one for the bug where objdiff would pair up two different symbols when their compiler-generated names just happened to be the exact same thing, which was rare but sometimes happens in enormous TUs.

A side effect of how I fixed this means that it no longer pairs up symbols with the same name but wrong section, i.e. if you forget to mark something const and it goes in .data instead of .rodata, it won't automatically pair those two up now. I think this side effect is desirable anyway? Since the TU won't match if you put data in the wrong section, even if it is equivalent. And whether data is const or not can effect function codegen too, so considering them different may be helpful for noticing these errors.