upgrade rq to v0.10.4
upgrade rq to v0.10.4

Newer rq uses newer toml library which provides more better output when
parsing errors occur.

With rq v0.9.2 (using [toml v0.2.1](https://github.com/dflemstr/rq/blob/v0.9.2/Cargo.lock#L27))
```
[ERROR] [rq] Encountered: control character `\n` must be escaped
```

With rq v0.10.4 (using [toml v0.3.1](https://github.com/dflemstr/rq/blob/v0.10.4/Cargo.lock#L472))
```
[ERROR] [rq] Encountered: newline in string found at line 14
```

Habitat itself uses rq ([only in one
place](https://github.com/habitat-sh/habitat/search?utf8=%E2%9C%93&q=_rq_cmd&type=))
to [pluck out exposed/exported ports from a plan's
default.toml](https://github.com/habitat-sh/habitat/blob/1fb090b35943dd013128f49588287a3114dadd06/components/plan-build/bin/shared.sh#L64).
This would improve error messaging when there is something awry there.

The changes to this plan are mostly around the new way upstream offers
their precompiled assets. Names changed. Contents changed. And it's
cross-compiled, but now needs some patchelf rubbed upon the build.

The elf patching occurs after unneeded symbols have been stripped from
the binary because strip does not like the modifications patchelf makes.
The dynamic loader should resolve any needed libraries via the RPATH.

If there comes a point where the hab-builds-hab primordial soup
bootstrap environment does not require rq, we could consider building rq
from source, but core would need a v8 engine package for this to depend
on to do that.

Signed-off-by: Robb Kidd <a629c362624370ec351e141df0bd1d27621ff790@thekidds.org>

be-plans/be,be-plans/be,be-plans/be,be-plans/be