Similar to #5342 where darc update-dependencies got support for subscription ID to simulate what a subscription would do, we should have the same for the darc vmr forwardflow and darc vmr backflow operations.

The subscription metadata could then be used in other places like excluded assets which we are currently leaving empty.