Few WorkManager fields are not MT safe

While debugging https://github.com/eclipse-jdt/eclipse.jdt.core/issues/4370 I've noticed that in the `org.eclipse.core.internal.resources.WorkManager` few fields are not volatile/atomic but could be accessed from different threads, so even if the modification happens while holding workspace locks, other threads might see stale values.

Fields in question are
- `WorkManager.operationCanceled`
- `WorkManager.nestedOperations`
- `WorkManager.preparedOperations`

I don't have reproducer, but I think making the fields either volatile or atomic shouldn't harm.

Comienza localizando org.eclipse.core.internal.resources.WorkManager y siguiendo los accesos concurrentes a operationCanceled, nestedOperations y preparedOperations. Determina si el uso existente del bloqueo del workspace todavía permite lecturas obsoletas; se considera terminado cuando los campos tienen una visibilidad segura entre hilos sin cambiar el comportamiento de WorkManager.

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