fix(idm): allow filein tags in mfsim.nam options block

[mjreno]

This PR addresses the error below. This issue can be seen following #1763 which adds a FILEIN style tag to the mfsim.nam options block in support of parallel.

ERROR REPORT:

  1. IdmLoad allocate simnam param unhandled datatype: RECORD HPC6 FILEIN
     HPC6_FILENAME

UNIT ERROR REPORT:

  1. ERROR OCCURRED WHILE READING FILE 'mfsim.nam'

[jdhughes-dev]

@mjreno The failures with test019_VilhelmsenLGR and test019_VilhelmsenLGR_nr seem to be related to recent dfn and/or idm changes. These tests are reading idomain for the parent in as a 3D array. The model is a multi-layer model.

I can get the tests to pass locally with the idm source files on develop. The tests do not pass if I regenerate idm files from the dfns in the repo. I get a different error related to the HPC file.

Not sure what is going on but it is affecting all of PRs.

[mjreno]

Thanks @jdhughes-usgs I'll check it out.

[christianlangevin]

Yeah, I'm seeing the same thing locally. I pulled all the latest, and my tests are failing with

ERROR REPORT:

  1. IdmLoad allocate simnam param unhandled datatype: RECORD HPC6 FILEIN
     HPC6_FILENAME

UNIT ERROR REPORT:

  1. ERROR OCCURRED WHILE READING FILE 'mfsim.nam'

[mjreno]

@langevin-usgs @jdhughes-usgs that error should be addressed with this PR. The test019_VilhelmsenLGR failures are FloPy errors that are happening when it is loading test model input and seem unrelated.

[christianlangevin]

Do we need to accept this failing PR and then address the idomain loading failure?

[mjreno]

If the FloPy issue is unrelated it seems like it could be addressed and then most of these tests should pass- is the Build ReadTheDocs failure related?

However it might make sense to merge this PR sooner than that to get people unblocked locally.

[wpbonelli]

@mjreno the RTD failure was my fault, it has since been fixed in the mf6 examples repo

[christianlangevin]

It seems there is still some sort of error with a flopy idomain load. I haven't been able to track it down yet.

[wpbonelli]

I think that is the same issue as here, @spaulins-usgs and I spoke briefly Friday, it is related to the change in flopy's array reading behavior introduced with modflowpy/flopy#2053, but we did not come to a resolution

[christianlangevin]

This is passing now. Will merge.