Network operations are "asynchrony". Together with parallelism, they are both kinds of concurrency and Swift concurrency handles both.
Swift's "async let" is parallelism. As are Task groups.
async let and TaskGroups are not parallelism, they're concurrency. They're usually parallel because the Swift concurrency runtime allows them to be, but there's no guarantee. If the runtime thread pool is heavily loaded and only one core is available, they will only be concurrent, not parallel.
Sure, but as soon as they released their first iteration, they immediately went back to the drawing board and just slapped @MainActor on everything they could because most people really do not care.