[Feature] Provide docs and samples about how to properly setup TLS client authentication and ACLs

Nobody has claimed this yet.

### Willingness to contribute

No. I cannot contribute a bug fix at this time.

### Feature Request Proposal

We need examples about how to make TLS mutual auth work and then ACLs

### Motivation

> #### What is the use case for this feature?

### Details

_No response_

### What component(s) does this bug affect?

- [ ] `Controller`: This is the control-plane for Venice. Used to create/update/query stores and their metadata.
- [ ] `Router`: This is the stateless query-routing layer for serving read requests.
- [ ] `Server`: This is the component that persists all the store data.
- [ ] `VenicePushJob`: This is the component that pushes derived data from Hadoop to Venice backend.
- [ ] `Thin Client`: This is a stateless client users use to query Venice Router for reading store data.
- [ ] `Fast Client`: This is a stateful client users use to query Venice Server for reading store data.
- [ ] `Da Vinci Client`: This is an embedded, stateful client that materializes store data locally.
- [ ] `Samza`: This is the library users use to make nearline updates to store data.
- [ ] `Admin Tool`: This is the stand-alone client used for ad-hoc operations on Venice.

The issue names no files, tests, or entry points; begin by surveying the Venice documentation and the TLS client-authentication and ACL configuration used by the Java project. Done means clear, working mutual-TLS and ACL setup examples are documented, but the requested scope and validation steps need maintainer clarification.

Written by the indexing model from the issue text.