fix: custom matchers are not available when using createHttpFactory()

[xemlock]

Custom matchers are not available when using createHttpFactory().

It may have been a deliberate decision to add custom matchers only to DOM-related contexts ( component, directive, host or pipe), but:

• they are available with createServiceFactory(), which does not necessary imply using components or DOM
• documentation doesn't say that these matchers are not available in some contexts, making errors like:

  TypeError: expect(...).toHaveProperty is not a function
  

  quite unexpected to the developer. Especially when it happens in some tests, and not in others.

Some matchers are not necessarily DOM-only, and could be used in more general contexts, for example toHaveProperty(). Also,

expect(obj).toHaveProperty('foo');

is definitely much better developer experience than:

expect(obj).toEqual(jasmine.ObjectContaining({ 'foo': jasmine.anything() }));

And better DX is what Spectator is all about.

So, for consistency, it would be nice to have custom matchers available regardless of the factory being used, which includes tests using createHttpFactory. Which this Pull Request is attempting to solve.

---

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/spectator/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix (kind of?)
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

TypeError: expect(...).toHaveProperty is not a function in tests using createHttpFactory. The error doesn't occur in tests using other factory functions (e.g., createServiceFactory).

Issue Number: N/A

What is the new behavior?

Custom matchers are available in tests using createHttpFactory.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.