Fix naming of MLSTUDIO module (#756)

### Feature or Bugfix
<!-- please choose -->
- Bugfix


### Detail
- Fix `ModuleName` for `MLSTUDIO` 
- MLStudio in the Environment Overview `Features` Card will not load
since the current `ModuleName.ML_STUDIO` property does not exist

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).
NA
```
- Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
  - Is the input sanitized?
  - What precautions are you taking before deserializing the data you consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires authorization?
  - How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?
```

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

frontend/src/modules/Environments/components/EnvironmentFeatures.js

@@ -29,7 +29,7 @@ export const EnvironmentFeatures = (props) => {
     {
       title: 'ML Studio',
       enabledEnvVariableName: 'mlStudiosEnabled',
-      active: isModuleEnabled(ModuleNames.ML_STUDIO)
+      active: isModuleEnabled(ModuleNames.MLSTUDIO)
     },
     {
       title: 'Pipelines',