The people that link you to those help articles are doing so because they simply can't do anything else but to escalate - they simply don't know about the inner workings of the system and don't have the permissions to change the data in it.
Whereas the developers/maintainers who could do it would be overcome with thousands of such mundane requests to fix the data in some geospatial database, that they can't be bothered to do. Perhaps Uber doesn't even maintain the dataset for addresses themselves either, and is using a service from someone else, like Google.
This kind of makes you think that in this complexity of distributed, scalable systems with microservices, message queues and other systems, eventually the complexity will be too much to actually understand and maintain - be it because of a low bus factor and people leaving due to churn rate, or extremely high effort needed for maintenance.
At this point, I don't give a shit about the $16 of paint, I'm not spending two hours of my day to return this can of paint at the lowes store on the other side of town. It's about the principle. A sane company would have replied with the first (and only) customer support team with something like "I'm so sorry! We are shipping you the correct color right now." That sane response used to be the norm 10 years ago, because a $16 loss on one can of paint is far less than losing a customer for life who will now make it their life's mission to deter friends and family from patronizing your business.