Orc 50 - Simplified the way the processor address is supplied

[solvicode]

For some background, there are two addresses (or IPs) at play:

• The address of the gRPC server that the processor get's exposed on
• The address that the orca core service queries in order to reach the processor

When orca core and the processor are on the same local network these two addresses are the same. But, when using the orca cli (for example), these are different as orca core is sitting inside a docker network. It has to reach the host network via a static IP.

In any case, the port in both these scenarios is the same, and the processor is always exposed on [::] - i.e. all network interfaces. So we can collapse the two env vars into 1 and just split out the port and address.

[solvicode]

FYI @christywastaken. These changes will mean that only one env var is require for the processor:

PROCESSOR_ADDRESS

And it will take the form of <host>:<ip>.