Removing code duplication in feature test

The verification on the expectors was run twice in the feature test for the
integration of mocking frameworks. Tests still pass, maybe a millisecond faster.

- The original spec had a double-slashed path like
  '/Code/gems//arbitrary'.
- Stubbing `Dir.getwd` forced the implementation to
  use that, but we'd like to reuse `RSpec::Metadata.relative_path`
  which does not use `Dir.getwd` internally.

- doesnt_match_inclusion_pattern_unless_system_exclusion?
  has a double negative and was being used in a compound
  conditional, which made my head explode. I couldn't
  understand it at all.
- Reuse `Metadata.relative_path` rather than having our own
  logic to do that.
- It'll perform better to get the relative path once rather
  than doing it once per pattern in the `patterns.any?` block.
- Add spec for case that is covered by a cucumber scenario but
  not by an existing spec (an earlier version of this commit
  broke that cucumber scenario but no specs failed, revealing
  the missing spec coverage).

…ion_from

describe parameters can now be classes without error

Conflicts:
	Changelog.md

…g_directory

Ignore working directory when excluding system patterns.

Update rake task docs with note about LoadError

[ci skip]

Add placeholder for code_or_symbol to NullColorizer