Upper year CS major here. I'd say start with whatever you feel comfortable with. Some will say you have to start with Big Java: Early Objects and read every word, others will say you must start with C/C++ or python if they're more lax. Personally, I think all you really need is a project to keep you motivated to learn. Whether it be a website for yourself to display your resume and achievements, a simple game that you create, or just an everyday utility tool that you have found a use case for.
Stay motivated! And use a project you are interested in to facilitate your learning.
While you are learning HTML/CSS and Javascript, keep that work in Git. You can run a repo on your own PC, you don't need a github account. Or you can use a github account, up to you. Also look into courses on UI design and user experience, color selections and design aesthetics. I don't know what these courses will be called. There are a bunch of other languages that are missing from your list though: C#, asp.net, .net, PHP, and Java are the ones off the top of my head.
Be aware that, of programmers, web developers are actually some of the worst paid. Good ones can make bank, but that's true in any profession. There's a massive difference between "I'm a programmer who writes middleware applications at cloud scale" and "I design the front end UI of our application." One of them is mostly a graphics designer with a little bit of programming, the other is mostly a programmer with a little bit of understanding of user experience. The latter gets paid far more (70k vs 120k).
Going forward you'll want to look into how to build cloud scale apps. Which also means how docker works, and how databases work. At large companies this work will all be siloed off away from you, but at a small company (<100 people) you might be asked to do it all yourself. The modern web page is not just a web page, it's an entire infrastructure of dozens of components all linked together.
The modern web page has a server side app that it is interacting with to determine what shows up on the page. Once you have the basics of building a web page down, 99% of your work should focus on that client-server interaction and understanding APIs/how to use them.
If it has a giant beefy heatsink, remove it to prevent board damages. If it's closed loop water cooling... Leave that in.
Remove the dedicated GPU. Biggest issue here as it can destroy the PCI-e slot in transit.
HDDs as well if you really want to make sure your data is fine.
And... That's it.
Fans, SSDs and what not are fine to stay in.
