Solver spec needs little modifications

[fracappa]

Hi everyone.

This issue address a specific misbehavior of the FLUIDOS Node architecture which comes from the Solver CRD Spec.

More specifically, there are two different boolean flags that characterize if the REAR process and the next peering establishment is automated:

1. ReserveAndBuy
2. EnstablishPeering

If the first is set to true, the REAR Reservation and Purchase is then triggered automatically.
The same happens for the second flag: if set to true, the peering establishment is done automatically.

However, if a user set the first flag to false and the second to true, this configuration could lead to problems as there could be no remote cluster to peer to.

We should deeply analyze if it is better to change Solver CRD Spec or if we need to implement some verification logic (like a webhook) to prevent those possible issues.

Thanks,
Francesco