$reload() method on resources through resource-api

All resources and collections returned from resource-api have a
.$reload() method that sends off an http request for the latest entity
data. This method proxies directly to api.reload with the given resource
and original http config and returns the same promise.
$reload() now proxies original config to api.reload()

Since api.reload() reinitializes the config it is given, and $reload()
on resources and collections was passing the resulting (i.e.
initialized) config on every call, any default transformers were being
duplicated on each call. $reload() now proxies the original,
non-initialized config instead so no duplication occurs.
Resources loaded via a collection can $reload()

While collections properly had a $reload() method set for themselves, no
resources loaded within a collection had their own $reload() method.
Given that resources loaded in a collection are cached even for future
requests to .get(), this would make the existence of a $reload() method
completely unreliable.
Do not duplicate config transformers on reload

Whenever a reload took place, through api.reload() or $reload(), any
transformers (request, response, or path) were duplicated for
subsequent reloads. This bug was similar to a previous one that affected
all requests and involved only default transformers, but it differed in
that it was only now affecting reload requests and was not limited to
default transformers only.