"*" wildcard in "include" section filenames triggers memory access violation on Windows machines.

[pavlov2000uk]

Bug Report

Describe the bug
https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/yaml/includes-section does not describe wildcards usage. However, after looking at the code, there is a block that is responsible for globing in Windows machines. I have a simple config with wildcards that runs in Linux, in Windows triggers memory access violation.

To Reproduce

• Steps to reproduce the problem:
  Install fluentbit latest (4.0.9).

Bad example in Windows (works in Linux)
includes:

• ./conf_inputs_*.yaml

pipeline:
outputs:
- name: stdout
match: '*'

conf_inputs_1.yaml
pipeline:
inputs:
- name: dummy
tag: test.one
dummy: '{"message": "hello from input 1"}'
rate: 1

conf_inputs_2.yaml
pipeline:
inputs:
- name: dummy
tag: test.two
dummy: '{"message": "hello from input 2"}'
rate: 1

Same config with absolute names works well Windows/Linux
includes:

• conf_inputs_1.yaml
• conf_inputs_2.yaml

pipeline:
outputs:
- name: stdout
match: '*'

Expected behavior
Expected behavior is that "*" wildcard and globing should work same way in Linux and Windows

Your Environment
Windows test - Microsoft Windows [Version 10.0.22631.5909] / Fluentbit 4.0.9
Linux test - fluent/fluent-bit:latest

[edsiper]

fixed in #10915