Parse Server option cannot be set via environment for interfaces

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

A Parse Server option cannot be set via environment variable if it is part of an interface. The reason seems to be that buildConfigDefinitions.js generates Definitions.js and adds the definitions for each interface into a separate module export. These definitions are then not part of module.exports.ParseServerOptions which seems to be the only export the Parse Server CLI considers.

Side note, that logic seems to be the reason why older Parse Server are all on the same root level and not grouped in nested objects, which is to consider for https://github.com/parse-community/parse-server/issues/7069.

Steps to reproduce

For example, idempotencyOptions has these sub keys:

idempotencyOptions: {
  paths: ...,
  ttl: ...,
}

The Definitions.js file only contains the root key PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_OPTIONS in module.exports.ParseServerOptions. The CLI runner only imports module.exports.ParseServerOptions therefore, setting environment variable PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_PATHS has no effect when initializing Parse Server.

Actual Outcome

All interfaces should be configurable via environment variables.

Expected Outcome

Only root key is configurable via environment variable.

Workaround

E.g. for idempotencyOptions the root key value can be set to an encoded object:

"PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_OPTIONS": "{\"paths\":[\"functions/.*\"]}",

Failing Test Case / Pull Request

• 🤩 I submitted a PR with a fix and a test case.
• 🧐 I submitted a PR with a failing test case.

Environment

Server

• Parse Server version: 4.5.0
• Operating system: irrelevant
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): irrelevant

Database

• System (MongoDB or Postgres): irrelevant
• Database version: irrelevant
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): irrelevant

Client

• SDK (iOS, Android, JavaScript, PHP, Unity, etc): irrelevant
• SDK version: irrelevant

Logs

Start with buildConfigDefinitions.js and the generated Definitions.js, then trace which export the Parse Server CLI imports for environment configuration. Reproduce the idempotencyOptions example with PARSE_SERVER_EXPERIMENTAL_IDEMPOTENCY_PATHS and inspect the existing configuration tests. Done means interface subkeys are recognized from environment variables while root options continue to work.