Fix clean_inactive for Filestream input

[belimawr]

Proposed commit message

The clean_inactive parameter was being parsed with the wrong key. It
is parsed/used by an anonymous struct on input-logfile/manager.go,
there it was parsed and used as CleanTimeout (clean_timeout). This
CleanTimeout setting has got exactly the same effect as the
clean_inactive described in our documentation.

This commit fixes this bug by renaming clean_timeout to
clean_inactive so the configuration value can have effect.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• Wait for Fix Filestream store GC, entries are now removed when they TTL expires #38488 to be merged and rebase onto main

How to test this PR locally

All files are at the end of this section.

1. Start Filebeat using filebeat.yml
2. Create the file to be ingested/write some data

   echo "foo bar" > /tmp/log.log
   

3. Look at Filebeat logs to ensure the file has been found, ingested and the reader was closed. Look for logs messages like those:

   A new file /tmp/log.log has been found
   Reader was closed. Closing. Path='/tmp/log.log
   

4. Ensure the store clean up run and removed the only entry, look for a log message like:

   1 entries removed
   

5. Ensure the registry log file (data/registry/filebeat/log.json) contains an remove operation like this:

   {"op":"remove","id":5}
   

filebeat.yml

filebeat.inputs:
  - type: filestream
    id: "test-clean-inactive"
    paths:
      - /tmp/log.log

    clean_inactive: 3s
    ignore_older: 2s
    close.on_state_change.inactive: 1s
    prospector.scanner.check_interval: 1s

filebeat.registry:
  cleanup_interval: 5s
  flush: 1s

queue.mem:
  events: 32
  flush.min_events: 8
  flush.timeout: 0.1s

path.home: %s

output.file:
  path: ${path.home}
  filename: "output-file"
  rotate_every_kb: 10000

logging:
  level: debug
  selectors:
    - input
    - input.filestream
  metrics:
    enabled: false

Related issues

• Closes: Filestream ignores clean_inactive #36629
• Needs: Fix Filestream store GC, entries are now removed when they TTL expires #38488

## Use cases
## Screenshots
## Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @belimawr? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 133 min 14 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[rdner]

Also, the linter issue needs to be fixed.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-clean-inactive-v2 upstream/fix-clean-inactive-v2
git merge upstream/main
git push upstream fix-clean-inactive-v2

[belimawr]

This is unrelated to the PR, but when I run mage check it got generated.

[belimawr]

/test

[nimarezainia]

Thank you all.