Fix resolving devices by defining the correct search key

[Talkabout]

When defining a device, for example, in the address module, it fails due to the wrong search key when calling find_by_key in _resolve_entity.

Due to the fields needed for a device entity in phpIPAM API:

$ curl -sk -XGET -H "phpipam-token: ${PHPIPAM_TOKEN}" ${PHPIPAM_API_URL}/tools/devices/ | jq '.data[0] | {id: .id, hostname: .hostname, ip: .ip}'
{
  "id": "8",
  "hostname": "Test device",
  "ip": "192.2.0.222"
}

By introducing an extra case for controller tools/devices we can override the default search key with hostname.

[cmeissner]

@Talkabout, thank you for filing this pull request. I updated the description a bit for others to better follow what it will achieve.

I also added a test case for that special combination of address and device to be sure the code is working. Also, a short changelog fragment was added to have a corresponding entry in the changelog of the upcoming version.

After granting you the permissions to trigger actions to run on push, I also realized that something seems to be broken. I will try to investigate on this issue, if I found time. You are also invited to invest some time to get to the root cause of that failure in CI.

[Talkabout]

@cmeissner Thanks for taking care!