Bolt in rmuiv2 to work with the new RASENMAEHER v2 rest api, at PoC or MVP level

Once rmapi design is locked enough it is time to build the poc for the mvp experience doing this end to end.
Bolt present rmuiv2 to drive the new RMv2 rest api and see what happens.

Acceptance criteria

• [ ] No ui design things past what's absolutely necessary, just see how the end to end flow works now
• Consider the microfront/MF setup's requirements in our new kubev2 environment, implication: alter the MF setup if needed, write down to the new product integration spec as needed.

IF:

• If there's a lot work to reconcile (heh heh) rmuiv2 to the brave new world, this task outputs a PoC => new tasks to actually align the uiv2 to here.
• If there's not lot work to do reconciling it, just round the edges so that we get the present experience with minimal extra work. If eg. group management is absolutely needed for a mvp, then implement it in a rudimentary form.

Start by reviewing the rmapi design and the existing rmuiv2 flow, then assess how it should drive the new RMv2 REST API end to end. Check the microfront/MF setup against the new kubev2 environment and update the product integration spec as needed. Done means either a PoC with follow-up alignment tasks or a minimally adjusted present experience, including only essential MVP behavior.