internal/v4: do not create new revision if content matches latest

When the content is the same as the latest version, there's no need to
bump the revision number. We needed to add another bundle to
test this, hence the change to the charm.v3 dependency.
Ok, I presume we pass it to avoid all fields to be retrieved.