engine: Functions registering bug

[DanCodedThis]

Problem

• If a function can be re-registered mid service execution it's not registered in the embucket-functions
• It is rather registered in the core-executor, which means:
  • Both the cargo update-functions command adds them back to the unimplemented list each time you run it
  • And the python script which add them to the implemented csv removes them from there
• This happens since they are nowhere to be seen in the standard registering place

Impact

Each time you add a new function, after running the commands. You need to:

1. Remove them from the unimplemented list
2. Add them back to the implemented csv

This is a big hassle since it's not even ctrl+c -> ctrl+v since they are in alphabetical (lexigrapical) order, you need to manually add each portion by hand. Which is tedious and a big hassle.

Possible solution

Move the cargo update-functions logic and the python script logic into the core-executor. Or provide them the context that those functions do actually exist. Or retire this approach for a better one.