Skip invalidating the 4xx-response cache tag for customer profiles on save

Follow up from 📌 Skip 4xx-response cache taag. Active

I was just about to follow-up that I'm still seeing one 4xx-response cache tag invalidation, but that's not from commerce_order but from the profile entity being saved. That's a bit trickier, because while not for us/typical commerce site, there can be cases where profiles are public and could have aliases and what not, so it's not as simple for profile as it was here. Still a useful improvement, as it's now 1 instead of 5 or so invalidations and only when users actually fill out and submit the checkout. But not quite as impactful as I was hoping.