[Enhancement] Implementing device adoption

[DiscoRiver]

Summary

I'd like to implement the v3 adoption resource into DeviceClient: https://console.us.code42.com/swagger/index.html?urls.primaryName=v3#/default/adoption

Proposed API

    def adopt(self, adopting_device_guid, adopted_device_guid):
        """Performs a device adoption.
        `REST Documentation <https://console.us.code42.com/swagger/index.html?urls.primaryName=v3#/default/adoption>__

        Args:
            adopting_device_guid (int): The device performing the adoption.
            adopted_device_guid (int): The device being adopted.

        Returns:
            :class:`py42.response.Py42Response`
        """
        uri = u"/c42api/v3/device/adoption"
        data = {
            u"adoptingGuid": adopting_device_guid,
            u"adoptedGuid": adopted_device_guid,
        }
        return self._session.post(uri, data=json.dumps(data))

This should be a fairly straightforward change, but I'm wondering if DeviceClient is the right place for it? Thoughts would be appreciated :)

[alanag13]

@DiscoRiver what does it mean for a device to be "adopted" by another device? Trying to think of how we could adjust the method name/documentation to make this more clear.

[DiscoRiver]

In the client app it shows as "replace device", which may be more user friendly.

Essentially, the "adopting" device takes over the GUID, archive, and settings of the "adopted" device, and becomes it.

[antazoey]

What happens to the original device? Is it deactivated?

[DiscoRiver]

The "adopting" obtains the identity of the "adopted", and is then deactivated. So the "adopting" GUID is the one to be deactivated.

[DiscoRiver]

@alanag13 @unparalleled-js - Did you both have any suggestions on how we might change the naming of this method? My thought was to have it as replace_device, which should fit in with the language we see on the client and in the console.

[DiscoRiver]

@unparalleled-js - Is this something you're happy for me to create a PR for?