Fix file.managed omitting mode from changes when creating a file

[HarnageaGabriel]

Summary

• check_file_meta() in salt/modules/file.py has two early-return points that fire when the target file does not yet exist (lstats falsy). Both skipped the entire mode/user/group comparison block, so file.managed only ever reported {'newfile': name} (test=True) or a diff (real run) when creating a file — never the mode being applied. When the file already existed, mode/user/group changes were reported correctly.
• This makes it impossible to audit, from state output alone, what permissions a newly-created file will get (e.g. mode: '0600' vs an unspecified umask-derived mode produce byte-identical changes).
• Fix: on the new-file paths, report the requested mode/user/group directly (there's nothing to diff against), guarded the same way as the existing-file case (skipped on Windows). Both early-return points are updated so behavior is consistent regardless of new_file_diff.

Fixes #69969

Test plan

• Added unit tests in tests/pytests/unit/modules/file/test_file_check.py covering a nonexistent target path with mode/user/group specified, for both new_file_diff=True/False, and for the ignore_ordering/tuple-return path.
• Verified existing-file behavior is unchanged (no regression).
• Added changelog/69969.fixed.md.

Note: ran pytest tests/pytests/unit/modules/file/test_file_check.py on Windows; the OS-gated tests (skip_on_windows) skip there since mode/user/group aren't applicable on Windows — the fix's logic was additionally verified directly against check_file_meta() with salt.utils.platform.is_windows() patched to False, confirming the new/existing-file paths behave as expected.

🤖 Generated with Claude Code

[welcome]

Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here's some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

• Salt's Contributor Guide
• Join our Community Discord
• Salt Project YouTube channel
• GitHub Discussions

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at saltproject.pdl@broadcom.com. We're glad you've joined our community and look forward to doing awesome things with you!