Reserve IP address for out of bounds machines

Ability to define IP address beside of choosing VMs in Static NAT, Port Forward and Load balancer services to provide those services to servers outside of CloudStack.
##### ISSUE TYPE

* Feature Idea

##### COMPONENT NAME

~~~
VR
~~~

##### CLOUDSTACK VERSION

~~~
All versions
~~~

##### CONFIGURATION

Advanced networking

##### OS / ENVIRONMENT

N/A

##### SUMMARY

In some network services we need to specify which VM should use it. For example Static NAT, Port Forward and Load balancer.
It would be a good idea if we can also specify IP address of a server which is not managed by CloudStack.
This feature helps us to use network services provided by virtual router for physical servers or even VMs outside of CloudStack management area but share a common L2 network with other VMs in CloudStack.
This feature also requires reserve IP address capability in all type of networks. We can expand the issue #4357 for private IPs in isolated networks too.

##### STEPS TO REPRODUCE

~~~

1. Create an isolated network
2. In Port forward section define a new rule
3. In "Add VM" panel write IP address of the server outside of CloudStack

~~~

##### EXPECTED RESULTS

~~~

An iptables rule created in virtual router to forward desired port to the server IP

~~~

##### ACTUAL RESULTS

~~~

It is not possible to mention IP address of the server outside of CloudStack

~~~

Comece pelas implementações do roteador virtual do CloudStack para Static NAT, encaminhamento de portas e balanceamento de carga, e consulte a issue #4357 sobre o trabalho relacionado à reserva de IPs privados. Está concluído quando esses serviços puderem direcionar o tráfego para um IP fora do gerenciamento do CloudStack e o roteador virtual criar a regra de encaminhamento correspondente em todos os tipos de rede compatíveis.

Escrita pelo modelo de indexação a partir do texto da issue.