Fix nested include with env files

[Vigilans]

Currently in model loading, workingDir refers to the relative directory to the workingDir of upper caller, instead of the process's current working directory. This makes operations like os.Stat(filepath.Join(workingDir, f)) will fail if invoked on such workingDir in nested include/extends.

This PR fixes such calling in ApplyInclude's env file handling logic, to use options.ResourceLoaders to retrieve the correct absolute path, instead of relying on filepath.Join(workingDir, f).