https://www.google.com/intl/en/ipv6/statistics.html
Anecdote, my ISP gives us IPv6 but not my employer. We use the IT equipment till the last breadth. I have seen, permanent table-fan running towards Floor's network hub. I guess that one is NOT IPv6 ready. :D
Maybe companies use the same opportunity to make sure their services also work via IPv6. But they won't stop offering their services on IPv4, and AWS changes don't put meaningful pressure on ISPs to roll out IPv6. If anything it will reduce the pressure on the price of IPv4 addresses, making it more viable for ISPs to hold out.
I doubt it, especially that there is an option of using private/CGNAT ranges instead of adopting a whole new protocol. Everyone who cares about IPv6 have already done their part, and people who don't care about it will likely use the lower-friction option, and between private IPv4 networks and IPv6 I bet that a lot of people will see private IPv4 as a lower-friction option.
Of course you can do all this via IPv4 by setting up proxies or gateways, but that's more work and more moving pieces than checking the checkbox that you want a public IPv6 and having it just work ... provided everyone you want to talk to talks IPv6.
The more likely story is places using AWS pay 1$/m for a public address and use private/IPv6 internally. I.e. an incremental step, not a revolution in the chart.
IPv6 adoption is not uniformly distributed. Some usersbases might have higher penetration. But yeah, I doubt there are many where it's high enough to be worth it.