Story: Refactor the AWS Thing type support

[kbeaugrand]

Description

When developing AWS support (#1865), we decided to update our functionality to support AWS specificity.
We should now improve this.

Acceptance criteria

• APIs should be behind the device model (the backend should do the job),
• Screens should not be changed,
• Depreciation should be handled by the backend when deleting the thing type (maybe a sync job to delete depreciated types, ...),
• Searchable attributes should be internal attributes managed by the portal (device id, device name, model id, ...) at this time I don't see any usage of searchable attributes on the model we will discuss aout that on the devices,
• The model should give the possibility to manage the properties (attributes in AWS, that are stored in the database and then pushed to the devices)