`microsoft.graph.managedDevice` is missing a filter restrictions annotation.

Filtering is only partially supported on /deviceManagement/managedDevices (microsoft.graph.managedDevice), but there is no Org.OData.Capabilities.V1.FilterRestrictions annotation on the type or on the deviceManagement/managedDevices navigation property. The only place the restriction is recorded is the type description:

Devices that are managed or pre-enrolled through Intune. Limited support for $filter: Only properties whose descriptions mention support for $filter may be used, and combinations of those filtered properties must use 'and', not 'or'.

With FilterRestrictions absent, Filterable defaults to true, so the metadata advertises the collection as fully filterable. Generated clients follow the metadata: Get-MgDeviceManagementManagedDevice exposes -Filter and the .NET client exposes Filter on the request configuration, with no machine readable signal about which properties actually work. Today a caller has to read the description of each property one at a time to find out.

The per property descriptions already record which properties support $filter, so the information needed for the annotation is already in the metadata.

Same shape as #225, which was fixed by #227.

Start by comparing this issue with #225 and its fix in #227, then inspect the managedDevice type description and the deviceManagement/managedDevices navigation property metadata. Done means the existing per-property filter support is represented by a FilterRestrictions annotation so generated clients no longer treat the collection as fully filterable.