terraform-provider-google: Weird state error with TF 0.14.0 on changes

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Problem

I think there is an issue with terraform 0.14.0 causing bad state to happen on changes. See https://github.com/hashicorp/terraform-provider-google/issues/7944 for the first time it happened. I got a similar error with cloud map:

When expanding the plan for google_compute_url_map.default to include new
values learned so far during apply, provider
"registry.terraform.io/hashicorp/google" produced an invalid new value for
.map_id: was cty.NumberIntVal(3.092957057560021842e+18), but now
cty.NumberIntVal(3.092957057560022e+18).