Adding support for the apiVersion parameter and other in the sfdx-project.json

[Alfystar]

Hello everyone!

With reference of the issue #3093, I am here to propose to the salesforce team to add the possibility to set the apiVersion parameter also inside the configuration file: sfdx-project.json.

In this way it would be possible to share and keep aligned the configurations of all developers of a project with the most suitable configuration in the current development branch.

In reality it would be fantastic if all the salesforce options, currently configurable with:

sf config set ...

Could be set as key-value pairs, inside sfdx-project.json
and get a similar result:

{
    "packageDirectories": [
      {
        "path": "src",
        "default": true
      }
    ],
    "name": "Enel CRMT",
    "namespace": "",
    "sfdcLoginUrl": "https://login.salesforce.com",
    "sourceApiVersion": "62.0",
+    "apiVersion": "61.0"
  }

Currently, to achieve a similar result I read the file with jq and apply the content of this key, but it is not a stable solution and requires that all the devs in my DevOps pipeline use this script, it would be preferable to integrate the application of these settings directly inside sf, with the usual priority orders: (example for sourceApiVersion)

1. element in the manifest file ( package.xml).
2. sourceApiVersion property in the sfdx-project.json file.
3. --api-version command flag.
4. SF_ORG_API_VERSION environment variable.
5. org-api-version local configuration variable.
6. org-api-version global configuration variable.
7. Highest API version supported by the target org.

Thank you so much!
I hope to have a positive feedback for this idea