[EKS] [request]: publicAccessCidrs should not be listed when an EKS Cluster is Private

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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

**Tell us about your request**
When an EKS Cluster is updated from Public to Private, the public access cidr list should from the previous configuration must be deleted.

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
When an EKS Cluster is converted from Private to Public, it asks for a set of Public Access CIDR list, 0.0.0.0/0 is default value. When the same cluster is converted to private from public, the vpc config shows the public access cidr list. Instead it must be an empty list

When the cluster is created without public access

```
"resourcesVpcConfig": {
"endpointPublicAccess": false,
"endpointPrivateAccess": true,
"publicAccessCidrs": []
.
.
.
},
```

When the cluster is converted to public and private
```
"resourcesVpcConfig": {
"endpointPublicAccess": true,
"endpointPrivateAccess": true,
"publicAccessCidrs": [0.0.0.0/0]
.
.
.
},
```

When the cluster is converted back to a private cluster
```
"resourcesVpcConfig": {
"endpointPublicAccess": false,
"endpointPrivateAccess": true,
"publicAccessCidrs": [0.0.0.0/0]
.
.
.
},
```

**Are you currently working around this issue?**
We are checking if the cluster is Public before showing the Public Access CIDR list to user.

**Additional context**
The public Access CIDR is not shown in AWS console after converting back to private cluster.

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)