Use dynamic resolution of SQS to allow working without it.

[anuraaga]

Using reflection is probably the worst possible solution but the simplest for now. Some ideas that come to mind for improvement.

• Add an annotation that can suppress classes from muzzle, similar to animal sniffer IgnoreJreRequirement. We'd be expected to thoroughly code review suppressed classes
• Have a system for defining classes that operate on plugins of the instrumented library.

interface PluginInstrumentation {
  boolean isEnabled();

  ... various methods
}

Muzzle would implement isEnabled to return true only if the references check out. And instrumentation would guard calls into "various methods" with isEnabled. Muzzle could probably also verify this guard is happening with some work.

Fixes #2408

[anuraaga]

Implemented dynamic dispatch as a stopgap - it'd be nice if 1.0 doesn't have broken aws sdk v1 instrumentation :)

[mateuszrzeszutek]

I think that we could add a method annotation that both stops muzzle from analyzing it and wraps the method with try {...} catch (LinkageError) to make sure that the runtime won't blow up no matter what - we'd still need to make sure that there are appropriate ifs guarding the annotated code, catching an error should be the last resort.

The plugin approach would probably be really complicated to implement (and understand)