Feat: API call to query Enum values - continuation - semgrep fix (dat…

…a-dot-all#1445)

### Feature or Bugfix

- Bugfix


### Detail
- replace Object.assign for enums
 
### Relates
- data-dot-all#1435

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- 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.

Co-authored-by: Sofia Sazonova <[email protected]>

frontend/src/services/graphql/Shared/getEnumByName.js

@@ -26,11 +26,11 @@ export const fetchEnums = async (client, enum_names) => {
   const response = await client.query(
     getEnumByName({ enum_names: enum_names })
   );
+  let enum_dict = {};
   if (!response.errors && response.data.queryEnums != null) {
-    return Object.assign(
-      {},
-      ...response.data.queryEnums.map((x) => ({ [x.name]: x.items }))
-    );
+    response.data.queryEnums.map((x) => {
+      enum_dict[x.name] = x.items;
+    });
   }
-  return {};
+  return enum_dict;
 };