3rdparty/docker/bootstrap: Cleanup, little modernization

Change-Id: Icc16b3fca48ffe072aed06c495d93fc3c74deead

docker/bootstrap: ensure work volume exec, fix dependencies

Change-Id: I8b8d3a2f3b5a09063b183dc355407908cc2640f6
Reviewed-on: https://review.haiku-os.org/c/haiku/+/2763
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
Reviewed-by: waddlesplash <waddlesplash@gmail.com>

docker/bootstrap: rename init to prep to be consistent

Change-Id: Ie6dc9061b13b23997f84a1ffe886d7e09c242cf0

3rdparty/docker/bootstrap: Fix a few potential mis-steps during the bootstrap init

Change-Id: I381fd7c00957e9d6797b0a79beacdef981593d3f

3rdparty/docker/bootstrap: Fix defaults to be more generic and engine selection

Change-Id: I8a1e3c6bd641ea08a5a06985389269d708d94655

docker/bootstrap: Improve local code injection

Change-Id: Ib1961d829ef1418a9b64307c73a01bab3520279a

docker/bootstrap: A few tweaks to your life easier

Change-Id: I591e108f9a5007423a5dee541e94b2be2342c5a8

3rdparty/bootstrap: kill any running bootstrap containers before rm

Change-Id: Id36226f121d4a75adc4799ae6cd8cddff2149b10

docker/bootstrap: Add extra gcc bootstrap requirements

Change-Id: Icacba4faaaab7e9af2b04225f99ef00ea4753606

docker/bootstrap: Add a few tools to bootstrap in a container

* The bootstrap process will pick up on local toolchains such
as clang and use them instead of the correct gcc cross-tools.
* This limits environmental factors which can break bootstrap.

Change-Id: Iacdd2a44cf26e18f838c9251fb9eddfbcb12565e