(fix) Fixing examples/03 and examples/05, seperating JS API from Paws natives

Got messy, having one `infrastructure` bag that I was trying to expose as both the JS API for this
library *and* the Paws-side API. So, I'm going to be putting methods *on the JS objects* for calling
from the JS-side, and keep the execution-bags exclusively for calling from within the reactor (thus
providing the context they need implicitly.)