GUI operation to store objects to a Git repository should consider folders recursively

Current Behavior

• When storing scheduling objects from the JS7 inventory to a local Git repository using the recursive option, which is intended to include all sub-folders when the -Folder parameter is used, it does not work as expected.
• The GUI calls the /inventory/deployables and /inventory/releasables API, however, it does not consider results. Instead the GUI stores files based on folder specification to the repository. This misses the user's options to decide if released/deployed object, valid/invalid objects should be deployed.

Desired Behavior
When storing scheduling objects from the JS7 inventory to a local Git repository using the recursive option, it should store all objects from the top-level folder as well as from all sub-folders and their nested folders. This ensures that all scheduling objects from the specified folder and its entire folder hierarchy are added to the repository.