--chugin-probe incorrectly says chugin is OK

[nshaheed]

There's a discrepancy between the new chugin error reporting and --chugin-probe:

If I improperly define a chugin, I now get these nice new error messages:

[chuck:2:SYSTEM]:  | loading chugins...
[chuck:3:HERALD]:  | searching 'C:\Users\nick/Documents/ChucK/chugins'
[chuck:2:SYSTEM]:  |  | (error) imported class 'Hydra' extends 'UGen'...
[chuck:2:SYSTEM]:  |  |  |- but does not contain UGen functions (e.g., tick)
[chuck:2:SYSTEM]:  |  |  |- (hint: chugin missing QUERY->add_ugen_func()?)
[chuck:2:SYSTEM]:  |  |  |- (origin: C:\Users\nick/Documents/ChucK/chugins/Hydra.chug)
[chuck:3:HERALD]:  |  | [FAILED] loading chugin Hydra.chug (8.1)
[chuck:3:HERALD]:  |  |  | reason: unsuccessful query in dll 'C:\Users\nick/Documents/ChucK'
[chuck:3:HERALD]:  |  |  | skipping 'C:\Users\nick/Documents/ChucK/chugins/Hydra.chug'...

However, if I do chuck --chugin-probe, everything seems hunky-dory:

[chuck:2:SYSTEM]: probing chugins in search paths...
[chuck:2:SYSTEM]:  | searching 'C:\Users\nick/Documents/ChucK/chugins'
[chuck:2:SYSTEM]:  |  | [OK] chugin Hydra.chug (8.1)

I guess the probe is only validating the api versions, not actually trying to load the chugins? This may be out of scope for probe itself, but I think the probe text should be more clear about what it's probing exactly.