Chore: Update configuration.environmentId docs

[liranfarage89]

Issue & Steps to Reproduce / Feature Request

resolves : #347

Since Zip doesn't use environment.configuration but only configuration with environment scope, a solution for using both is irrelevant.

There was a misunderstanding regarding their usage but eventually, we decided to update the docs by describing that using configuration.environment_id requires ignoring changes of environment.configuration

The issue with allowing both is that configuration requires an environment, so at the first run, the environment will be deployed without configuration variables. From the 2nd deployment, there will be a drift because the configuration resource metadata will be retrieved by the API of the environment.

In other words, those are 2 ways to manage the same resource so only one way should be picked. ( preferably the environment.configuration to prevent the first usage issue )

Solution

Add ignore changes requirement in configuration.environment_id description

[liranfarage89]

Find a better solution to Zip's environment scope config vars on TF Provider