Prepare executor VMs

[nesitor]

Problem: Launch executor VMS the first time, take some time for new executor functions.

Feature: Added a preload script of the executor function to candidate CRNs, and if the CRN doesn't respond, add it to unauthorized_node_list file.

[MHHukiewitz]

LGTM

[MHHukiewitz]

LGTM

[MHHukiewitz]

@hoh approve plz

[hoh]

I have a few questions regarding the logic here:

1. Why use an unauthorized_list of nodes that did not respond instead of an authorized_list of nodes that did respond ?
2. Can you explain the motivation to hardcode this list in the function squashfs ? I assume that it is for transparency reasons, but that should be explained somewhere else we'll never remember in a few months...
3. I don't see any docstring on the new functions to explain what we use them for and what they do on a high level. Can you add this ?

Apart from these 3 questions, I made some suggestions to improve the quality of the code with suggestions that you should just be able to apply on the code.

[nesitor]

I have a few questions regarding the logic here:

1. Why use an unauthorized_list of nodes that did not respond instead of an authorized_list of nodes that did respond ?
2. Can you explain the motivation to hardcode this list in the function squashfs ? I assume that it is for transparency reasons, but that should be explained somewhere else we'll never remember in a few months...
3. I don't see any docstring on the new functions to explain what we use them for and what they do on a high level. Can you add this ?

Apart from these 3 questions, I made some suggestions to improve the quality of the code with suggestions that you should just be able to apply on the code.

1.- Because if we use an authorized_list of nodes, if the users add new CRNs to the network, we will just limit to the nodes added, instead to also use the new ones.

2.- You need to hardcode the list to use it inside of the function. Yes, you can load the list as a volume also, but this should be done as another future, and also ensure to publish the list independently, that will complicate the deployment.

3.- Indeed I don't added so much important methods, and all are used inside of the logic. The important external methods are already documented.

[MHHukiewitz]

Could this help with some of the VRF problems we encountered recently @nesitor ?