feat(pegboard): expose rivet server from within containers for docker compose (#2628)

<!-- Please make sure there is an issue that this PR is correlated to. -->

## Changes

<!-- If there are frontend changes, please include screenshots. -->

Author: NathanFlurry

docker/dev-full/docker-compose.yml

@@ -213,14 +213,16 @@ services:
       - RUST_LOG=debug,hyper=info
     stop_grace_period: 0s
     depends_on:
+      # HACK: rivet-server dependency since we need to do a DNS lookup in entrypoint.sh for the iptables chain
+      rivet-server:
+        condition: service_healthy
       rivet-edge-server:
         condition: service_healthy
       foundationdb:
         condition: service_healthy
     volumes:
       # - ./rivet-client/entrypoint.sh:/usr/local/bin/entrypoint.sh:ro
       - ./rivet-client/config.jsonc:/etc/rivet-client/config.jsonc:ro
-      - ./rivet-client/rivet-actor.conflist:/opt/cni/config/rivet-actor.conflist:ro
       - client-data:/var/lib/rivet-client
     ports:
       # Enable host networking for actors

docker/dev-full/rivet-client/config.jsonc

@@ -2,7 +2,18 @@
 	"client": {
 		"runner": {
 			"flavor": "container",
-			"use_resource_constraints": false
+			// Resource constraints are not supported in Docker
+			// TODO: Needs further investigation in to why nested cgroups v2 resource constraints aren't working
+			"use_resource_constraints": false,
+			"custom_hosts": [
+				// Define host for the API server
+				//
+				// This is a custom IP defined in entrypoint.sh iptables
+				{
+					"ip": "192.168.100.1",
+					"hostname": "rivet-server"
+				}
+			]
 		},
 		"cluster": {
 			// This is safe to hardcode