iOS 18 Apple Music queue issue (forces old queue all the time)

Been hoping they'd fix this by now but as it's still ongoing, I thought I'd come here to see if anyone might have some sort of solution. Old Apple Music had it so if I instant-played a song from an album (just tapping it to play it), then it would naturally clear the old queue, and replace the queue with the rest of the album. If I had any songs in a previous queue from an old listening session, Apple Music would be smart enough to know that I wanted to hear the new album I tapped on, and would thus clear the old queue. This was nice because if I wanted to start a new listening session, and leave the old one behind, it would naturally clear that old queue, and if I wanted to retain the old queue, I could simply add songs to "play next" or "play after." Not anymore. Now, when I tap on a new song, it retains the old queue. I can't simply tap the first song on an album and expect to listen to the whole album. Instead, if I do it the way I used to, it will play the first song of that album, and then proceed to resume my old queue. To prevent this, I now have to go into my queue, clear it, THEN tap the first song of an album. But of course, since this is different from how it's been done for literally the last ENTIRE EXISTENCE OF ITUNES AND APPLE MUSIC, I constantly make the mistake of trying to play an album by simply tapping the first song.

This also applies if I'm not even trying to listen to an album. Let's say I play a song, then proceed to add a bunch of other songs to "play next" and "play after," because I'm crafting my queue for the next thirty minutes or so. Well, even the "play next" button doesn't actually play next! Instead, Apple Music will default to playing the PREVIOUS QUEUE FIRST. It's especially bad when my old queue was on infinity mode. If I was playing off of infinity mode during my last listening session, it will play an INFINITE number of songs before it ever gets to my "play next" queue. I'm thoroughly confused and can't imagine this is how the feature is actually supposed to work. Does anyone else experience this??