Fix Environment retrieve methods

[DimaMishchenko]

Description 📝

Fix of Environment variable retrieve methods provided in #1468

Currently this functionality works incorrect.
If variable is not exists, dynamicMember will return nil and getString/getBoolean will never be called.
Also in case if variable exist and you use helper methods you still will get optional value.
Can be fixed by creating extension to Optional type.

Example

// appName not exists

// before
Environment.appName?.getString(default: "TuistApp") // nil

// now
Environment.appName.getString(default: "TuistApp") // "TuistApp"

Checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase.
• The changes have been tested following the documented guidelines.
• The CHANGELOG.md has been updated to reflect the changes. In case of a breaking change, it's been flagged as such.
• In case the PR introduces changes that affect users, the documentation has been updated.

[fortmarek]

Hi @DimaMishchenko! Changes look good, as mentioned, it'd be great to make this change non-breaking

[fortmarek]

Looks good to me - I'd just change the deprecation message but otherwise 👍 from me

[kwridan]

Good catch @DimaMishchenko - thanks for fixing this 👍

One additional suggestion would be to perhaps update the fixture https://github.com/tuist/tuist/blob/main/fixtures/framework_with_environment_variables/Project.swift to leverage the new syntax.

[DimaMishchenko]

Done. Thank you @fortmarek and @kwridan

[fortmarek]

let's merge this once CI is green, unfortunately, we have some issues on main. We should re-run the tests here once that is fixed.

[pepicrft]

@all-contributors add @DimaMishchenko for code

[allcontributors]

@pepibumur

@DimaMishchenko already contributed before to code

[fortmarek]

@DimaMishchenko could you please rebase and see if the pipeline succeeds now? The main should be fixed now. Sorry for the additional troubles 🙂