when deploying a bundle, resource revisions are ignored

[Cynerva]

Deploy a bundle that includes something like this:

services:
  flannel:
    charm: cs:~containers/flannel-339
    resources:
      flannel-amd64: 3
      flannel-arm64: 1
      flannel-s390x: 3

Instead of getting the specified bundle revisions, you'll get whichever revisions the charm store gives you (in this case, the latest resources from the edge channel). In contrast, if you deploy via Juju CLI, you will get the specified revisions.

The issue occurs here, where the resources that are passed in do include the revision numbers, but that parameter is ignored.

[johnsca]

Specifically, I think this needs to honor resource IDs that are already given and only use the ones from the store which are not explicitly specified.