Use latest docker images main

[michellemcdaniel]

No description provided.

[michellemcdaniel]

Please note: this is still broken on the centos 7 image. I don't know why and i haven't been able to figure out how to run the tests locally or in a way that I can debug the failure. The diff of the files between the image previously used and this one is here: https://github.com/dotnet/dotnet-buildtools-prereqs-docker/compare/3e800f15050c4514ee36c7bebffed95cd8dad287..6124dd8d705e266effaffcbb5eca10d9278df8d2#diff-ed6a3ef6bd766531bc5a2c02a93521cf1527017f893a3423b72dbba4501098bd. I could use some help from the diagnostics folks on how to dig into this. The big changes that I can see is moving lldb from 3.9.1 to 9.0, and doing some of the build of llvm/lldb in a scl shell.

This appears to be the error message:

STDIN: 00:00.235: runcommand process launch -s
00:00.236: (lldb) runcommand process launch -s
00:00.271: error: process launch failed: 'A' packet returned an error: 8

[mikem8361]

I wonder if this is the seccomp profile (CAP_SYS_PTRACE) that allows ptrace on the new image (if that is possible I don't know). @hoyosjs might.