dird: enable default options in fileset config when no options are explicitly specified

[alaaeddineelamri]

Description

When a fileset configuration does not include an options section, the default values would not be applied. Defaults would only apply when the config parser finds an options section.

This PR makes sure default options are set even when no options section is specified.

Please check

• Short description and the purpose of this PR is present above this paragraph
• Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

• Git Workflow
• Automatic Sourcecode Formatting
• Check your commit messages

Checklist for the reviewer of the PR (will be processed by the Bareos team)

General

• PR name is meaningful
• Purpose of the PR is understood
• Commit descriptions are understandable and well formatted
• Check backport line
• Is the PR title usable as CHANGELOG entry?
• Separate commit for CHANGELOG.md ("update CHANGELOG.md"). The PR number is correct.

Source code quality

• Source code changes are understandable
• Variable and function names are meaningful
• Code comments are correct (logically and spelling)
• Required documentation changes are present and part of the PR
• bareos-check-sources --since-merge does not report any problems

Tests

• Decision taken that a test is required (if not, then remove this paragraph)
• The choice of the type of test (unit test or systemtest) is reasonable
• Testname matches exactly what is being tested
• On a fail, output of the test leads quickly to the origin of the fault

[pstorz]

This is a very nice and elegant solution for the problem. What I am missing is a test that prooves that the value values are correctly set even if a fileset has no options block. That can probably be added quickly to a gtest.

Best regards,

Philipp