Fixes 16536 - Fix filtering of device component by device role

[Alef-Burzmali]

Fixes: #16536

Fix the filtering of device components by device role by aligning the name of the fields from the DeviceComponentFilterForm and the DeviceComponentFilterSet.

I saw two solutions to implement the fix:

1. Rename the fields in the DeviceComponentFilterSet to device_role_id and device_role (that's the one I've implemented)
2. Rename the field in the DeviceComponentFilterForm to role_id but create an exception for InventoryItemFilterSet and InventoryItemFilterForm, which already have a field named role for the InventoryItemRole

I've chosen solution 1 because:

• We are not filtering according to the component's role but according to its parent device's role, so device_role makes more sense as role could be confused with the role of the component.
• It avoids creating an exception for InventoryItemFilterSet, which would have its role field override the role field from DeviceComponentFilterSet, and would have needed a device_role field or equivalent to preserve the feature. The role filter of DeviceComponent would have a different meaning between an Interface or a InventoryItem, which would have been more confusing.
• While the release note for 4.0 clearly states in breaking changes that the device_role field of devices has been removed after a depreciation period, there are no mentions of DeviceComponent in the notes or in #13342, so it may have been an undocumented or unintended change
• There is no equivalent filtering on VMInterface, it's not possible to filter them by their VM's role at the moment, so the reason behind the renaming of "device_role" to "role" is not currently present for DeviceComponent. However, if this feature is added, a more neutral field name such as "parent_role" or "parent_object_role" could be used instead.
• It's the least amount of changes required for this fix. Solution 2 would have required modifying InventoryItemFilterSet, InventoryItemFilterForm, DeviceComponentFilterForm and the fieldsets of all inheriting FilterForms.

However, solution 1 also changes the API to filter the device components by roles. This was an undocumented change in 4.0, so maybe that's acceptable.

Please let me know if you agree with that approach or if you prefer another solution.