[compiler] multi-project config does not support `noFutureProofEnums` config

Trying to consolidate two relay compilation steps by adopting the multi-project config but the multi-project config does not support the `noFutureProofEnums` flag.

```shell
[ERROR] Unable to initialize relay compiler configuration. Error details:
Error searching config: Invalid config file: "/Users/mikeldking/work/arize/arizeweb/relay.config.json": Error parsing JSON: The config file cannot be parsed as a multi-project config file due to:
- Error("unknown field `noFutureProofEnums`", line: 0, column: 0).

It also cannot be a single project config file due to:
- Error("unknown field `projects`, expected one of `schema`, `src`, `artifactDirectory`, `include`, `extensions`, `excludes`, `schemaExtensions`, `noFutureProofEnums`, `language`, `customScalars`, `eagerEsModules`, `persistConfig`, `isDevVariableName`, `codegenCommand`, `jsModuleFormat`, `schemaConfig`, `moduleImportConfig`, `typegenPhase`, `featureFlags`", line: 0, column: 0).
```

Expected behavior is to support the same flags as the single project setup.

Start with the multi-project configuration parsing path and compare its accepted fields with the single-project configuration, using the reported relay.config.json shape as the reproducer. The work is done when a multi-project config accepts noFutureProofEnums and the same setting remains supported for single-project configs; the payload does not name a source file or test.

Written by the indexing model from the issue text.