Add consensus client to `fullnode.dappnode` feature

[pablomendezroyo]

The fullnode.dappnode is an alias added to the selected execution client by the user. This way, other dappnode packages can use this alias to make requests to the execution client. Add to the existing feature fullnode.dappnode the consensus client selected.

• fullnode.execution.dappnode => execution client selected
• fullnode.dappnode => execution client selected (for backwards compatibility)
• fullnode.consensus.dappnode => consensus client selected

[alexpeterson91]

I like it. Good use of up-cycling of what was an essentially deprecated feature or at least one that sees very little use anymore. I am Curious what the endpoint would be if using the multicaster for your full node with idk geth priority 1 and besu at priority 2 selected with Teku as the driving consensus client. Would fullnode.execution.dappnode use the load balanced execution Multicaster execution engine endpoint http://execution-multicaster.dappnode or would it use the highest priority execution layer selected in the multicaster. In this example geth. ? Idk the current status of the multicaster either I suppose so this may not have even been a consideration yet. But will be relevant eventually.

[pablomendezroyo]

Would fullnode.execution.dappnode use the load balanced execution Multicaster execution engine endpoint http://execution-multicaster.dappnode

@alexpeterson91 yeah! thats a good point to add to the issue

[pablomendezroyo]

@dappnodedev whats the status?