Before changing any System Files, I would recommend having a Backup because things can go wrong especially when you are dealing with Terminal. The alternative is to just do a Clean Install and manually add the apps and verify the Kernel Task operation to isolate the problem. The Clean Install may be the easiest approach to quickly return your Mac to a stable operation, but if you want to attempt manually remove the files that are modifying the system files, then continue on:
https://mac.install.guide/homebrew/5
- Uninstall Xcode Command Line Tools
https://mac.install.guide/commandlinetools/6
https://docs.docker.com/desktop/uninstall/
- Verify VSCode has been removed from your User folder. The folder is hidden so you will have to use Command-Shift-.(period), to reveal it. Show the folder by going to Finder > Go > Go to Folder and enter "~" (tilde character)
- In addition, I would go to Finder > Go > Go to Folder, and enter ~/Library/LaunchAgents, and remove all Google files. There is also some kind of issue with the valvesoftware plist that you see there as it is showing that the "Executable not found", which may be due to an unsuccessful installation.
- Go to Finder > Go > Go to Folder, and enter /Library/LaunchAgents, and remove com.apple.dt.xcode.xcbackgrounddownloader.plist if it is still there.
After restarting, I would post a follow up EtreCheck report to verify that the files have been removed. You are obviously a developer with many tools that have been installed with Terminal. A Mac with 8GB of RAM is not enough for the extensive set of Developer Tools that have been added. You would be better served with just Xcode, but of course that depends on your development goals, and even then the RAM will be restricting performance and it will need to rely on VM that slows performance, but at least you can quit Xcode and it does not impact your system. I suggested removing the Google files because I have seen other users with those same "keystone" files that are "Not Signed" showing "Empty", that have been a problem.
This should stabilize your OS and calm down your Kernel Task. You can experiment by comparing the results of installing the files you want back with the operation of the Kernel Task.