Ember+ plugin accepts unsupported URI schemes in session configuration and silently uses TCP for the connection.

This may be confusing because a user can specify a scheme such as udp:// and expect a different connection type, while the plugin actually connects over TCP without any warning or error.

Step to reproduce:
1. Configure an Ember+ session with an unsupported scheme:

Plugins.EmberPlus.Sessions.test.Uri=banana://127.0.0.1:9000

2. Restart Zabbix Agent 2.
3. Request: ember.get[test,1]

Actual results:
The request succeeds. The provided URI scheme is ignored and the plugin connects to 127.0.0.1:9000 using TCP. The same behavior can be reproduced with schemes such as udp:// and https://.

Expected results:
The plugin should not silently use TCP when another URI scheme is specified. Unsupported schemes should either be validated and rejected with an error, or the behavior should be handled in another clear way so that the user does not expect the specified scheme to be used.