Integrate tee worker configuration into oracle config management

[mudler]

Problem

Since we integrated the tee worker code in #613 we have now the following env vars:

    TEE_WORKER_URL: an URL to a tee-worker service
    KEEP_SEALED_DATA: keep data sealed and do not decrypt it. This is useful when running the oracle aside to another protocol that wants to relay encrypted data (e.g. should be enabled when running it aside with the bittensor code).
    PRINT_PUBKEY: If enabled, it will make the oracle print only the pubkey (used to instrument e2e tests, not meant to be useful for users)

which are not tight to the viper and pflags settings.

Acceptance criteria

the scope of this card is to tie the env vars to the app config as all the other environment variables and get rid of the tech debt introduced in #656