Peripheral API v3.0.2: Stable peripheral locations

[garbear]

Description

This PR introduces a small backwards-compatible addition to the Peripheral binary add-on API. It adds simple comparison operators to the utility class.

This change is required by xbmc/peripheral.joystick#294.

Motivation and context

By enabling comparison, we can assign the same peripheral index when a controller is unplugged/replugged. This feature will be important in my upcoming Player Manager.

How has this been tested?

Tested on Ubuntu 22.04.

I made a quick change so that peripheral locations would show in the Player Viewer instead of the driver name:

--- a/xbmc/games/agents/windows/GUIAgentList.cpp
+++ b/xbmc/games/agents/windows/GUIAgentList.cpp
@@ -209,7 +209,7 @@ void CGUIAgentList::OnEvent(const ADDON::AddonEvent& event)
 void CGUIAgentList::AddItem(const CGameAgent& agent)
 {
   // Create the list item from agent properties
-  const std::string label = agent.GetPeripheralName();
+  const std::string label = agent.GetPeripheralLocation();
   const ControllerPtr controller = agent.GetController();
   const std::string& path = agent.GetPeripheralLocation();

I unplugged/replugged controllers randomly and observed that their location was preserved.

What is the effect on users?

• Player assignment will be slightly more stable when unplugging/replugging controllers during gameplay

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• Student submission (PR was done for educational purposes and will be treated as such)
• None of the above (please explain below)

[garbear]

jenkins build this please