ENV schema validation base on character cofiguration

[marc-aurele-besner]

ENV schema validation base on character cofiguration

At the moment, the env schema validation expect all envs to have values, regardless of the config of the character (aka what ai models the character will use).

As we increase the support for multiple models, this creates a barrier to entry, where a new user will feel like they need to have multiple API keys from multiple AI providers, while in reality, they could very easily set all the config to use open ai and just put fake data in all the other envs...

Ideally we should add a first layer that build the schemaValidator, base on the current config on the character. If only open ai is in use by this character, only open ai envs should be expected.