pymakr config setup depricated

* OS: Manjaro Linux rolling
* Micropy Version: v4.0.0-rc.2
* Python Version: 3.10
* VSCode Version: 1.7.30
* pymakr: 2.22.5

Hi,
I just setup my first project with the help of Micropy Cli on VSCode.
It seems the config Micropy is creating for pymakr in its currently available version from the extensions is deprecated.
Of all options set by Micropy only `safe_boot_on_upload` and `py_ignore` are still valid.

The proposed workflow sadly isn't working anymore and you currently have to upload each file manually.
I now downgraded pymakr to the last 1.x version. I guess either there needs to be an alternative flow to be implemented or this required version should be mentioned.

``` JSON
[{
"resource": "/home/XXX/projekte/micropython/water/pymakr.conf",
"owner": "_generated_diagnostic_collection_name_#3",
"code": "2",
"severity": 4,
"message": "Deprecated. Board address is stored in a persistent VSCode session.",
"startLineNumber": 2,
"startColumn": 5,
"endLineNumber": 2,
"endColumn": 30
},{
"resource": "/home/XXX/projekte/micropython/water/pymakr.conf",
"owner": "_generated_diagnostic_collection_name_#3",
"code": "2",
"severity": 4,
"message": "Deprecated. Board credentials are stored in a persistent VSCode session.",
"startLineNumber": 3,
"startColumn": 5,
"endLineNumber": 3,
"endColumn": 24
},{
"resource": "/home/XXX/projekte/micropython/water/pymakr.conf",
"owner": "_generated_diagnostic_collection_name_#3",
"code": "2",
"severity": 4,
"message": "Deprecated. Board credentials are stored in a persistent VSCode session.",
"startLineNumber": 4,
"startColumn": 5,
"endLineNumber": 4,
"endColumn": 25
},{
"resource": "/home/XXX/projekte/micropython/water/pymakr.conf",
"owner": "_generated_diagnostic_collection_name_#3",
"code": "2",
"severity": 4,
"message": "Deprecated. Please use the explorer context menu for upload/download of specific folders and files.",
"startLineNumber": 5,
"startColumn": 5,
"endLineNumber": 5,
"endColumn": 25
},{
"resource": "/home/XXX/projekte/micropython/water/pymakr.conf",
"owner": "_generated_diagnostic_collection_name_#3",
"code": "2",
"severity": 4,
"message": "Deprecated. This may or may not be reimplemented.",
"startLineNumber": 21,
"startColumn": 5,
"endLineNumber": 21,
"endColumn": 24
}]
```

Start by locating the Micropy CLI code that generates pymakr.conf and compare its options with the Pymakr version described in the issue. Reproduce the generated configuration with the current extension and verify whether the workflow works or whether the required Pymakr version must be documented. Done means the generated setup no longer relies on deprecated options, or the supported version and workflow are clearly identified.

Written by the indexing model from the issue text.