Fix Enum Flag Logic to Correctly Match Specific Flags

[WanjohiSammy]

Description

This PR addresses an issue with the Flags enum logic where the bitwise AND operation (graphValue & flagValue) != 0 incorrectly matches combined flags when only specific flags are intended.

The current logic (graphValue & flagValue) != 0 checks if any of the bits in flagValue are set. While this works for simple flag checks, it fails when combined flags are involved. For example, if Admin is a combination of Read, Write, and Execute, checking for Read and Write using the current logic will also match Admin, which is not the intended behavior.

[Flags]
 public enum AccessLevel
 {
     None = 0,
     Read = 1,
     Write = 2,
     Execute = 4,
     Admin = 7 // Read | Write | Execute
 }

To resolve this issue, the logic has been updated to (graphValue & flagValue) == flagValue, which ensures that only the specified flags are matched correctly. This change prevents combined flags from being incorrectly matched when checking for specific flags.