[feature]: create mission control profiles for payment/pathfinding related calls #7812
Description
Is your feature request related to a problem? Please describe.
Today we have two path finding algos, and a number of diff params for each aglo. If a user wants to experiment with all the new knobs they're able to dynamically modify the current params using the SetMissionControlConfig call. However this applies the config globally. This restricts certain cases of multi-user systems, and has a sort of race conditio nbuilt in as concurrent payment attempts by use diff configs.
Describe the solution you'd like
We should create a way to allow namespaced routing configs. Maybe one config is for smaller, more quickly resolving payments. Maybe another is for larger payments, that cares less about fees and the time of completion, etc.
Profiles should be able to be created and named using the routerrpc gRPC server. Any payment related calls should also optionally take a profile, to be used when carrying out path finding. We can assume that SetMissionControlConfig continues to modify the current "default" profile.
This functionality is very useful, as it can be used to perform A/B tests for a payment related service, without "polluting" other payment attempts or path finding calls.
Profiles should be kept on disk to ensure durability between restarts.