New Private field method access issue [Workaround]

## Current Workaround

So it seems this is the workaround for now. Any direct access the new field breaks the rewritter.

```c#
_instanceNewField.DoesWhatYouWant(); //<- fails to rewrite
var myLocalNewField = _instanceNewField; // <- this gets correctly rewritten
myLocalNewField.DoesWhatYouWant(); //<- All good
```
Then on your next recompilation round you can clean up the syntax.

## Issue
I'm not sure if it's a regression and what would be its reason, but most of the time nowadays adding private fields fails as they are not rewritten correctly in every places. Example bellow.
Added
`private CameraState _lastCamState;`

One of the correctly rewritten part I believe
`FastScriptReload.Scripts.Runtime.TemporaryNewFieldValues.ResolvePatchedObject(this)._lastCamState = state;`

Some other places not rewritten
` Gizmos.DrawWireSphere(_lastCamState.FinalPosition, BodyRadius);`

It is the NewFieldsRewriter job to perform the rewrite now not sure why it skip some cases.

Comienza con el NewFieldsRewriter y reproduce el caso reportado de acceso a un campo privado en el flujo de trabajo de recarga en caliente de Unity. Compara el acceso directo a _instanceNewField con la alternativa de usar una variable local y, después, verifica que usos como Gizmos.DrawWireSphere(_lastCamState.FinalPosition, BodyRadius) se reescriban de forma coherente sin requerir una limpieza de la sintaxis.

Escrito por el modelo de indexación a partir del texto del issue.