Support --privileged or --cap-add for docker containers

Describe the enhancement
Facilities for controlling how a runner's container are constrained to volumes, ports, and environment. This restricts the kinds of things that can be accomplished inside the container. In my specific case, I run my jobs as root in the container, and I'd like access to iptables.

Code Snippet
Proposed sample:

         container:
             image: connectedhomeip/chip-build-cirque:0.4.10
             volumes:
                 - "/tmp:/tmp"
                 - "/dev/pts:/dev/pts"
             env:
                 LOG_DIR: /tmp/cirque_test_output/
                 CLEANUP_DOCKER_FOR_CI: 1
             options: "--privileged"

Start by locating how the runner translates container settings such as volumes, ports, environment variables, and the proposed options field into Docker container creation. Validate the result with a workflow using options: "--privileged" and confirm that equivalent --cap-add settings reach the container.