When credentials in netrc file are changed, bazel still uses the old ones.

Hey, I have an issue related to netrc file.
When credentials in netrc file are changed, bazel still uses the old ones.
Version of **bezel 2.2.0**.

**Initial situation**
When building a file I got a 401 status code for some maven packages. Updated credentials in netrc files, but continued to get 401 status code.

A generated version of netrc file is created by bazel, e.g.
`/private/var/tmp/_bazel_etyurina//70547e7733fc96c4b2405a268b1d10f9/external/maven/netrc`

After updating credential in actual netrc file the generated version of netrc it is not updated. But bazel continues to use generated version of netrc with wrong credentials.

Would be glad for explanation what I am doing wrong.
If this is not the case, what changes need to be made to invalidate generated netrc file whenever actual one is updated?

Start by reproducing the Maven fetch after changing the actual netrc file, then compare it with the generated file at /private/var/tmp/_bazel_etyurina//70547e7733fc96c4b2405a268b1d10f9/external/maven/netrc. Trace how the generated netrc is refreshed and define done as preventing stale credentials from being used after the source file changes.

Written by the indexing model from the issue text.