Support profile mechanism

[relu91]

Currently, Scripting API does not provide any dedicated function for handling the Profile mechanism. We need to discuss whether we must support this starting from a use case or user story description.

Generated from #352

[zolkis]

We don't seem to need a function for handling the profile mechanism, which says that the property "profile" should be included with a valid URI.

On consuming, that is supported (via ConsumedThing.getThingDescription()).

On exposing, the init dict provided to produce() may contain it.

What other developer scenario is missing?

[danielpeintner]

There are 2 things that concern me when it comes to profiles

• profiles can not only subset the TD. In fact they can also superset the TD
• each profile may come up with certain constraints (that Scripting might need to check). Not sure if we can (and want) to add support for that