Both HTTP 1.0 and 1.1 and HTTP/2 are high-level network protocols, which work on the lower-level TCP protocol.
Imagine you’re talking to a person over the phone, HTTP would be the sounds you’re emitting, TCP would be the electrical signals that phones are sending to each other.
The HTTP/3 version (previously called HTTP over QUIC) is nothing more than a slightly modified version of HTTP/2 to work on the QUIC protocol instead of the TCP protocol.
The TCP protocol was created to ensure the delivery of the data sent, for this it uses some techniques that end up impacting the performance of HTTP/2. Primarily its multiplexing, which is when two or more data streams (e.g., two .js files) are transmitted at the same time within the same communication channel.
QUIC was created by Google to be a lighter and faster replacement for TCP. Switching TCP to QUIC allows the page to load faster and using less bandwidth. This already happens when you access Google servers using Chrome, because communication is done with QUIC.
In other words, HTTP/3 is nothing more than standardizing HTTP over QUIC so that all browsers and servers can communicate faster without any compatibility issues.
For now it is still a proposal, but given the performance improvement, the bandwidth saving and the support that QUIC is receiving from major web companies like Google, Facebook, Mozilla, Opera, Cloudflare and others, it is very likely that it will be adopted.
From what I read, what changes is just the "base" protocol, in case 3 it would be the QUIC (by what I read is UDP and not TCP, apparently developed by Google). Of course it has details and some other change. I will wait for the answers :)
– Guilherme Nascimento