feat: Enable deeplinks to device details page using hostname

[No9]

Currently the device details page is made available through the internal guid in the navigation path.
e.g. https://cloud.shellhub.io/devices/d1ae8d18090f7cb30e1bb827ec6775bd586c0394faacc98a7bc4c2990addce4d
This is a bit problematic for 3rd party integrations where an external systems would like to provide a link to the device remote connection capability in shellhub.
The problem is mainly due to some form of sync integration needing to be developed.
These can be brittle and lead to complexity due to features like compensating transactions being required during the device registration. This problem compounds as more backend management systems are added to the device.

However shellhub has a great feature in the registration process that allows for over riding of the hostname using SHELLHUB_PREFERRED_HOSTNAME.
This allows for a shared id to be established across different management systems greatly simplifying this problem.

To bring this full circle it would be great for the UI to support https://cloud.shellhub.io/devices?hostname=SHELLHUB_PREFERRED_HOSTNAME as a navigation feature directly to the device details page.

Let me know any thoughts on this feature.

[gustavosbarreto]

The ideal approach would be to retrieve the device UUID via the API, since the UID is immutable unlike the hostname. However, we are open to considering an alternative solution if there is a valid use case for this feature.

[gustavosbarreto]

I do see value in this use case and I believe it could be quite useful for integrations.

@otavio @henrybarreto , I would like to hear your thoughts on this as well.

[gustavosbarreto]

We discussed this request internally and now we have a clear proposal to support opening the device page using the hostname.

You can read the full proposal here: Device Resolution by Attribute

Summary:

• New API:

  GET /api/devices/resolve?hostname=...
  

  This returns the device response object for a given hostname.

• New UI route:

  /devices/:identifier?resolver=hostname
  

  When resolver=hostname is used, the UI will find the UID and open the device details page.

This makes integration easier and removes the need to sync hostnames and UIDs and also allows us to support other identifiers like MAC or serial number in the future.

[No9]

Thanks for looking into this - can't wait to see it land.