Improved overflow support: Internal EventHandlingWatch interface

[sungshik]

This PR adds a new internal interface, EventHandlingWatch, which extends the existing external interface ActiveWatch. In the next PRs, EventHandlingWatch will be generically used as a type in overflow event handlers instead of JDK...Watch. That's useful because these overflow handlers may also be used by non-JDK watches.

[codecov]

Codecov Report

Attention: Patch coverage is 61.53846% with 5 lines in your changes missing coverage. Please review.

Project coverage is 80.3%. Comparing base (53f3038) to head (9807fdb).
Report is 8 commits behind head on improved-overflow-support-main.

Files with missing lines	Patch %	Lines
.../engineering/swat/watch/impl/jdk/JDKFileWatch.java	0.0%	2 Missing ⚠️
...wat/watch/impl/jdk/JDKRecursiveDirectoryWatch.java	0.0%	2 Missing ⚠️
.../engineering/swat/watch/impl/jdk/JDKBaseWatch.java	66.6%	1 Missing ⚠️

Additional details and impacted files

@@ Coverage Diff @@## improved-overflow-support-main #19 +/- ##
==================================================================
- Coverage 80.5% 80.3% -0.2% - Complexity 91 94 +3 
==================================================================
Files 11 12 +1 Lines 416 428 +12 Branches 41 41 ==================================================================
+ Hits 335 344 +9 - Misses 59 61 +2 - Partials 22 23 +1 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[DavyLandman]

I want to keep ActiveWatch as small and focussed as possible.

[DavyLandman]

In a public interface, this feels a bit weird, I want to keep this interface as small as possible, to allow us to improve the API without breaking compatibility.

Maybe this should be an internal/private interface?

[sungshik]

Agreed. I've extracted handleEvent and relativize into a separate interface in the impl package, called EventHandlingWatch.

[DavyLandman]

Much better 👍🏼