MutationObserver.observe check for options argument is too strict

[romansp]

Describe the bug
MutationObserver.observe check for options argument is too strict and throws DOMException for the cases when it's valid according to the DOM Standard.

It should also throw TypeError and not DOMException in case when options object is invalid.

To Reproduce
Steps to reproduce the behavior:

1. Run the following code in 'happy-dom' environment

let div = document.createElement('div');
let text = document.createTextNode('old');
let observer = new MutationObserver(() => console.log('mutated'));
observer.observe(div, { attributeFilter: ['style', 'class'] });
observer.observe(text, { characterDataOldValue: true });

Expected behavior
Should not throw DOMException or TypeError.

Device:

• Version 13.1.4

Additional context
According to the DOM Standard the following steps should be performed first before checking options.

1. If either options["attributeOldValue"] or options["attributeFilter"] exists, and options["attributes"] does not exist, then set options["attributes"] to true.
2. If options["characterDataOldValue"] exists and options["characterData"] does not exist, then set options["characterData"] to true.

Discovered while running tests against codebase with VueUse usage. Here MutationObserver is used with just attributeFilter: https://github.com/vueuse/vueuse/blob/84965f53edc73b221804de91e565ffdf71d1e28d/packages/core/useElementBounding/index.ts#L96-L98