Since Android API level 31, location permission is no longer required for using Bluetooth APIs if developers strongly assert that their app doesn't derive physical location from Bluetooth scan results. This is done by setting usesPermissionFlags="neverForLocation" in the AndroidManifest.xml:

<uses-permission android:name="android.permission.BLUETOOTH_SCAN"
                 android:usesPermissionFlags="neverForLocation" />

However, the usesPermissionFlags attribute was not exposed in the .NET UsesPermissionAttribute, preventing developers from using this Android feature.

Changes Made

This PR exposes the usesPermissionFlags attribute by:

1. Making the attribute visible in metadata.xml to enable auto-generation by the manifest-attribute-codegen system
2. Adding comprehensive test to verify the attribute generates correct XML

The implementation leverages the existing auto-generation system instead of manual modifications, ensuring consistency with the codebase architecture.

Usage Examples

Developers can now use:

// Property assignment (auto-generated property)
[assembly: UsesPermission(Name = "android.permission.BLUETOOTH_SCAN", 
                         UsesPermissionFlags = "neverForLocation")]

This generates the correct AndroidManifest.xml entry as specified in Android documentation.

Fixes #10409.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.