settings.network.no-proxy: describe the defaults more clearly

**Path to page with content (_do not_ include domain name):**
en/os/1.20.x/api/settings/network/#no-proxy

**What content is incorrect?**
```
The no-proxy list automatically includes entries for localhost.

On Kubernetes variants (*-k8s-*) the no-proxy lists includes the Kubernetes API server endpoint as well as other commonly used Kubernetes DNS suffixes.
```
The example sets no-proxy entries for localhost.

The no-proxy list does contain the entries described here. These are never visible in apiclient, but are added to any entries from the API setting. Attempting to add no-proxy entries for localhost has no functional effect (Bottlerocket just ends up with no-proxy entries for localhost, twice).

**What should the content say or communicate?**
The content should include this behavior. Yes, bottlerocket will never proxy localhost, no, you can't override that behavior, and no, you will not see these automatic no-proxy entries in the API.

Open the documentation page at en/os/1.20.x/api/settings/network/#no-proxy and review the no-proxy description and example. Update the content to explain the automatic localhost and Kubernetes entries, that they cannot be overridden, and that they are not visible in the API setting; done means the page matches the reported behavior.

Written by the indexing model from the issue text.