Allow silencing broadcast for cache update methods.

[benjamn]

As discussed in #6262 (comment), it would be convenient to be able to silence the broadcast of cache updates for methods like cache.writeQuery, cache.writeFragment, and cache.evict.

While this was an easy change for writeQuery and writeFragment, which already accept various named options (see Cache.Write{Query,Fragment}Options), it was a bit trickier in the case of cache.evict, which instead has positional parameters: id: string, fieldName?: string, and args?: Record<string, any> (see #6141 if args is new to you).

Compared to named options, the ergonomics of positional parameters deteriorate rapidly as you add more parameters. Instead of continuing to fight that battle, I decided it was time to make cache.evict accept named options: Cache.EvictOptions. Passing id, fieldName, and args arguments still works as a backwards compatible alternative to Cache.EvictOptions, but we won't be adding any new positional parameters to cache.evict from this point forward. Any/all new cache.evict inputs (such as options.broadcast) will be added via Cache.EvictOptions.

⚠️ This PR is still very much in need of tests! ⚠️

[benjamn]

@hwillson Happy to split the options.readField changes out into a separate PR, if you like.

[hwillson]

@benjamn Keeping everything here together works for me, thanks!

[darkbasic]

I'm all in for named options. Also, since it's a new major release anyway, I'm also for deprecating the old syntax with positional parameters.