fix: properly-map-environment-name

[Zaimwa9]

Environment.name was wrongly mapped.

Added tests to mappers

[emyller]

1. Although the fix looks solid, is it relevant to get Environment.name available in the old engine?
2. Does this affect other behavior in the new engine? If so, we'll need to coordinate a team effort to update other SDKs. 😞

P.S. I also fixed "environment.name" in the fixture for the PHP client in order to map it correctly to the context, but didn't bother to make it useful in the old engine because seemingly it never was?

[emyller]

Approving because my previous questions aren't blockers.

[Zaimwa9]

The way I see it:

1. It doesn't impact the old engine. But at least in node, the flow is:

• Reading the document
• Creating models (including the EnvironmentModel) => That's where I need to make it available
• Mapper use the EnvironmentModel as a basis => That's where I need the name
  Basically, there is no "old engine" in Node, there are models that act as Data structure that have been preserved because it's still used in the sdk: make it useful in the old engine because seemingly it never was => This is spot on. It didn't exist, adding it wouldn't change the behavior of the old engine. Just an extra unused property in this old way

2. That's the fix. If we use the project.name it means that all the evaluation based on EnvironmentName would be wrong.