useIntersection: Update docu or differentiate between option-parameters

[FlxAlbroscheit]

As I was just working on a class that implements useIntersection, I wondered whether there is any way to pass the "threshold"-parameter to the underlying IntersectionObserver-class (see available options on MDN), as I was going to need some delay before appear and disappear-callbacks are being executed.

Turns out: It is indeed possible by simply adding "threshold" to the options-parameter of useIntersection (e.g. useIntersection(this, { threshold: 0.8 })). The official use-intersection docu does not mention anything about this possibility, instead it just mentions the stimulus-use-relevant options that are available. However, these options are simply passed further to new IntersectionObserver(...), as can be seen here and in the TypeScript-defintion of IntersectionOptions. The browser then probably simply "ignores" the options which are stimulus-use-specific, which is fine on the one hand, but a little bit verbose on the other.

I propose at least two ways to deal with this issue:

1. Add in the documentation of useIntersection the possibility to pass non-stimulus-use-specific options that are then passed further to create the internal IntersectionObserver instance (e.g. rootMargin or threshold).
2. Differentiate between options that are meant for useIntersection and those meant for IntersectionObserver.

[adrienpoly]

Fully agree with that I had the same use case recently and had to look to the source code