In regard of signals

[pBouillon]

Signals are the next big thing in Angular (as in many other web framework).
RxJS will also become optionnal in the upcoming versions, and maybe ngx-flagr should follow this trail.

I am not sure yet of what to do with signals and RxJS:

• Completely remove RxJS and only rely on signals? But how would feature flags be evaluated if this information is fetched over the internet?
• Make RxJS and signals stands side-by-side? But what about projects that's won't rely on signals anymore? I wouldn't like ngx-flagr to be the reason they still have rxjs as a dependency (which would most probably result in the removal of ngx-flagr)
• Ignore signals? But most API tends to use them and it will becore the norm for lots of other code bases as well
• Create a separate package just for signals in the same way NgRx did, but it might result in a lot of duplication in the case of ngx-flagr

Any take on the subject would be greatly appreciated as this is not a change I will do in a near future, but more to prepare the library for signal components.