[Bug]: Update parallel=False for open_mfdataset() as potential workaround to NetCDF: Not a Valid ID issue

[tomvothecoder]

What happened?

From: E3SM-Project/zppy#548 (comment)

Searching for the error NetCDF: Not a valid ID. I landed with a similar issue and a potential solution. To summarise in this thread, it looks like a work-around in netcdf4-python to deal with netcdf-c not being thread safe was removed in 1.6.1. The solution (for now) is to [make sure your cluster only uses 1 thread per worker](https://forum.access-hive.org.au/t/netcdf-not-a-valid-id-errors/389/14).

@tomvothecoder In this case, it might be worth to try by using parallel=False instead in xarray.open_mfdataset to try by passing this issue.

What did you expect to happen? Are there are possible answers you came across?

e3sm_to_cmip/e3sm_to_cmip/cmor_handlers/handler.py

Lines 399 to 407 in cb12e89

	ds = xc.open_mfdataset(
	all_filepaths,
	add_bounds=["X", "Y"],
	decode_times=False,
	combine="nested",
	data_vars="minimal",
	coords="minimal",
	parallel=True,
	)

Minimal Complete Verifiable Example (MVCE)

No response

Relevant log output

No response

Anything else we need to know?

No response

Environment

Latest stable version of e3sm_to_cmip and master branch