fix: priority of default deny read on macos

[shfx]

Hi. I noticed a maybe unclear or undefined behavior, please correct me if I'm wrong.

With this config, .env files are still accessible but should not be:

{
  "filesystem": {
    "defaultDenyRead": true,
    "allowRead": ["."],
    "denyRead": ["**/.env", "**/.env.*"]
  }
}

IMHO we want denyReads to take precedence over allowReads. I created this changeset that apparently works on my machine. If you think this is incorrect then maybe we can find better way of blocking important files when defaultDenyRead is true and we still want to have entire dir readable like ".".

Anyways, thanks for the project, it's pretty cool :)

[jy-tan]

Thanks for the fix @shfx! This makes sense. Could you also add coverage that fails on the actual precedence regression? e.g., assert the generated macOS profile includes explicit deny file-read-data / deny file-read-metadata rules for defaultDenyRead + allowRead "." + denyRead "**/.env", or add a darwin integration test showing .env inside the allowed workspace cannot be read. Thanks!

[shfx]

🙇🏻