some automatic Nomad and/or to Consul basic "Intentions" idea

My primary idea looks like this:
```
service {
name = "loadbalancer"
port = "80"
provider = "nomad"
address_mode = "driver"
intentions {
scope = "myappscope" // in this scope, app could talk to each other loadbalancer
ingress = undefined / true / ["myappscope", "or service"]
egress = undefined / true / ["myappscope", "or service"]
iamloadbalancer = true/false // if true, the service is a loadbalancer and we know loadbalancer ip
loadbalanceme = true/false/["myappscope", "or service"] // if true, the service can accept traffic from
// loadbalancer and we know loadbalancer ip
}
}

service {
name = "appnameservice"
port = "80"
provider = "nomad"
address_mode = "driver"
intentions {
scope = "mysecondapp"
loadbalanceme = true
}
tags = [
"traefik.enable=true" //....
]
}
```

scope - app in same scope could talk to each other
ingress/egress - could be controlled in scope or without scope
loadbalanceme - iamloadbalancer could reach this node ( lets 1 balancer talk to 3 apps isolated from each other but not load balancer)

this block could be transfered to Consul intentions
problem - iptables / ipset rules ( open services )

No files, tests, or entry points are named. Start by reviewing the proposed Nomad service `intentions` block and its possible Consul transfer, then clarify the scope, ingress and egress semantics and the intended iptables/ipset behavior. Done should include agreed semantics and an implementation plan.

Written by the indexing model from the issue text.