Make parseReserve import more explicit

[dvcrn]

Hi, under certain conditions, the import to parseReserve being .. is causing errors

In our case (just normal bundling through rollup) we weren't able to use any instructions (like withdraw) that are depending on parseReserve. The transpiled javascript object (__1) ended up undefined, so the call to parseReserve fails

After making the import more explicit everything is fine again, transpiled now looks like this:

const parsedData = (_a = (0, state_1.parseReserve)(new web3_js_1.PublicKey(this.reserve.address), buffer)) === null || _a === void 0 ? void 0 : _a.info;

Probably an edge case in the handling of .. for imports