Implement resource estimates in function api and lower levels #1992
Description
This would the next stage after:
ITISFoundation/mmux_vite#349
Since when users who run a function or map a function could possibly spend lots of credits, it would be good to be able to give them a warning with information like:
(1) which services/nodes will run, and using which pricing plan
(2) how much would this cost in total
Item (1) is relatively easy to implement, we would need to:
- for project functions, ideally create an endpoint in the project api that collects all this information about all the nodes in the project and returns i.
- for solver functions, we can probably straight access that information from the service
- add an endpoint to the function api to get that information
Item (2) is less deterministic in general. Since the actual cost can heavily depend on the user settings/scripts, we probably need to keep some statistics for project/functions. These could then be used for cost estimates.