Feature: Handle architecture mis-match

[strictlymike]

Using flare-qdb in a 64-bit Python interpreter on a 32-bit binary can yield misleading errors. An example, courtesy of Thomas Pullen:

C:\Users\whoever\>flareqbd "challenge3.exe" -at 0x0040105e "du('eax')"
qdb: [0x0040105e=0x40105e]: Vivisect expression parse exception: name 'eax' is not defined
[...stack trace ensues...]

At start-up, it would be nice if the user were warned that the architecture of the flare-qdb instance (i386 or amd64) does not match the architecture of the target binary in the cmdline positional parameter. Ideally, flare-qdb would instruct the user to install and use flare-qdb with a 32- or 64-bit installation of Python (whichever is appropriate) and retry it with this binary. Optionally, there might be a -f or --force flag that would suppress the error and allow people to limp by, specifying rax when they really mean eax, and so on.