Better management of properties

[FlorianJacta]

Description This issue aims to simplify the use of Taipy Studio Config.

We should only give the properties available for a storage type and not all the properties. For example, a Pickle Data Node cannot have "has_header", "db_username, "db_port", etc properties. If we only give the possible properties to the user, this will simplify the use of Taipy Studio/ Core, avoid errors and misunderstanding. The documentation on Data Node will also not be needed.

If all the properties of a Data Node are used for a Storage type, the button to add properties should disappear.

Acceptance Criteria

• [ ] Ensure new code is unit tested, and check code coverage is at least 90%
• [ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
• [ ] Ensure any change is well documented

[FredLL-Avaiga]

I thought the user could add its own properties ?

[FlorianJacta]

Taipy Studio Config should not suggest "db_username" for a Pickle Data Node even if they can add more properties to a DataNode Config. I don't see where it is in conflict with this issue

[FredLL-Avaiga]

If all the properties of a Data Node are used for a Storage type, the button to add properties should disappear.

that would conflict with this

[FlorianJacta]

I see. You could still have it, but it shouldn't propose anything then. You just have to write your own property.