UrlParams: Intend system update, split into configuration and propreties

[toger5]

Needed for implementing #3372 more cleanly

This PR updates the intend system. We want to solve this before starting on the telephone usecase implementation to prohibit us needing to make too many rust-sdk PR's and to converge to a solution we think brings the best benefits to maintain the url paramters.

This solution tries to get us the most features from this list:

• Authority in EC (change all platforms at once)
• Flexible usage of EC in other clients (secondary)
• Very simple/fast setup on EX (one prop preferably)
• As much transparency as possible (intent -> changes things the dev did not know about anymore) No time should be wasted on: “was this handled by an intent, do i need to look into the intent description, or do i need to look through feature list”
• No artificial entanglement (flexibility) If the intent “telephoneOneOnOne” controls “autoleave” (for example) we will always get “startUnmuted” if we want autoleave. Sometimes only one of them is desired.
• (off topic but related) We want EC to feel like a custom react component with properties. It can execute functions (send call member event, encryption keys) but things like “sendNotifyEvent” might be configurable as params

By implementing intends with a "preset" architecture:

• The intend is optional and it is possible to tweak each individual configuration
• Each intend is a list of presets that also adapt based on platform
• Web + EX configurations should only set the intend and keep all the other options blank. So everything can get controlled in the EC codebase.
• It is still possible to provide an intend but overwrite a subset of the configuration properties via individual query parametrs.

This PR changes:

• remove all deprecated fields
• split the url parameters into UrlProperties and UrlConfiguration (configuration are the ones where you can skip with one intend, properties are always required)

[robintown]

Suggested change

	* This UrlProperties contains as the properties that are used by to pass required data to the widget.
	* This UrlProperties contains the properties that are used by applications to pass required data to the widget.

[robintown]

Suggested change

	* and configure the behavior of the app. There value is the same if EC is used in
	* the same context but different accoutns/users.
	* and configure the behavior of the app. Their value is the same if EC is used in
	* the same context but with different accounts/users.

[robintown]

Suggested change

	if (value && Object.values(type).includes(value as T)) {
	if (value !== null && Object.values(type).includes(value as T)) {

To avoid surprises with falsy strings

[robintown]

What do you think about the idea of not including intent in the returned object here? That would enforce that we never predicate any behavior on the intent alone, and always provide some other URL parameter to override the behavior with.

[toger5]

let me check it was used for. But your explanation for why it is not needed (should not be needed) sounds very sane to me.

[robintown]

I think this should still be true.