Describe the bug
F3D doc states (https://f3d.app/doc/user/CONFIGURATION_FILE.html):

The following options are only taken on the first load: no-render, output, position, resolution, frame-rate and all testing options.

This is only true if such option are set in the "no-match" config block, but they are ignored if they are put in a match config block, even when loading a single file

Also multi-file-mode and recursive-dir-add are not mentionned in the doc, despite having the same limitations.

To Reproduce
Steps to reproduce the behavior:

Use the following config file:

[
  {
    "match": ".*vt.",
    "options": {
      "no-render": true
    }
  }
]

1. Open the file using f3d --config=/path/to/config cow,vtp
2. F3D is not using no-render, it should

Expected behavior
Documentation corrected or behavior corrected

Dev Notes
It should be pretty simple to use the file group when loading the options the first time instead of using an empty file group.

However multi-file-mode and recursive-dir-add cannot be taken into account in that case, so their doc should be clarified.

F3D Information
Paste the content of f3d --version or f3d-console.exe --version on Windows: 3.2.0

Additional context
Detected in the context of: #2437 (comment)