[9.2](backport #49553) update gosigar to v0.14.4

[mergify]

Proposed commit message

update github/elastic/gosigar to v0.14.4

This is done specifically to bring in elastic/gosigar#190, which will allow the filesystem metricset of the metricbeat system module to skip over volumes that don't exist on Windows. Examples would be transient, ejected or ghost volumes.

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. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Should provide more robust collection of filesystem metrics on Windows systems.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

---

This is an automatic backport of pull request #49553 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of b49ecb8 has failed:

On branch mergify/bp/9.2/pr-49553
Your branch is up to date with 'origin/9.2'.

You are currently cherry-picking commit b49ecb871.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt
	new file:   changelog/fragments/1773868374-update-gosigar-to-v0.14.4.yaml
	modified:   go.mod

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

🤖 GitHub comments

Just comment with:

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

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)