Incorrect use of fsnotify in configtls

[haoqixu]

Describe the bug
When working on #8395, I observed another testing failure:

=== RUN   TestErrorRecordedIfFileDeleted
Event: fsnotify.Event{Name:"/var/folders/9l/f2cn0_n52w38y4m77wms60gc0000gn/T/clientCAs.crt1808838314", Op:0x12}    clientcasfilereloader_test.go:65:
        	Error Trace:	/Users/haoqixu/code/personal/wip/otel/opentelemetry-collector/config/configtls/clientcasfilereloader_test.go:65
        	Error:      	Condition never satisfied
        	Test:       	TestErrorRecordedIfFileDeleted
    clientcasfilereloader_test.go:70:
        	Error Trace:	/Users/haoqixu/code/personal/wip/otel/opentelemetry-collector/config/configtls/clientcasfilereloader_test.go:70
        	Error:      	Not equal:
        	            	expected: "test error on reload"
        	            	actual  : "<nil>"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-test error on reload
        	            	+<nil>
        	Test:       	TestErrorRecordedIfFileDeleted
--- FAIL: TestErrorRecordedIfFileDeleted (5.00s)

Steps to reproduce
Run go test -v -run TestErrorRecordedIfFileDeleted -race -count 1000 . under config/configtls.

Environment
OS: macOS 13.2.1
Compiler(if manually compiled): go1.20.3

Additional context

The Op field of fsnotify.Event is a bitmask and some systems may send multiple operations at once. We should use the Event.Has() method instead of comparing with ==.

The failure above was caused by an multiple operations event.