clean up fsnotify module dependency

[leehinman]

Currently go.mod claims that beats requires fsnotify 1.6.0

github.com/fsnotify/fsnotify v1.6.0

This is because containerd v1.7.20 requires that version. However, farther down in go.mod fsnotify is replaced with

github.com/fsnotify/fsnotify => github.com/adriansr/fsnotify v1.4.8-0.20211018144411-a81f2b630e7c

This means that all versions of fsnotify will be replaced with the one specified, which is really based on v1.4.7, further complicating things the go.mod in github.com/adriansr/fsnotify contains the following:

require (
        github.com/fsnotify/fsnotify v1.5.1
        golang.org/x/sys v0.0.0-20211007075335-d3039528d8ac
)

Which means you always get v1.5.1, even if you try to specify the exact version that adriansr/fsnotify provides. This is a complicated mess. And means that any code that uses features that are only found in 1.6.0 won't be able to find the code.

Propose the following fix.

1. Elastic should create a new repo for a fsnotify fork, and merge in the 2 changes that are in the adriansr fork
2. Elastic should release a 1.6.0 version and 1.7.0 version of fsnotify with the 2 changes
3. Elastic should work on getting these changes in upstream so we don't have to maintain a fork

[elasticmachine]

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

[pierrehilbert]

Closing as #40956 is merged.