CodeQL Macos workflow

[andrewc12]

Motivation and Context

The different files included in the different builds might not be scanned if we build on only one system.

Description

Run codeql on a macos system to catch problems in macos specific code.

How Has This Been Tested?

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Performance enhancement (non-breaking change which improves efficiency)
• [ ] Code cleanup (non-breaking change which makes code smaller or more readable)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• [ ] Documentation (a change to man pages or other documentation)

Checklist:

• [ ] My code follows the OpenZFS code style requirements.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the contributing document.
• [ ] I have added tests to cover my changes.
• [ ] I have run the ZFS Test Suite with this change applied.
• [ ] All commit messages are properly formatted and contain Signed-off-by.

[andrewc12]

⚠️ This PR needs PR #12110 to be merged first ⚠️

[andrewc12]

@ryao just checking with you that we need OS specific codeql workflows.

[ryao]

@ryao just checking with you that we need OS specific codeql workflows.

Yes, although this should not be merged until MacOS support is merged.