I thought that VS Code did this for me but for some reason it seemed to
miss this one thing

One will explicitly assert what I meant for it too and there is a new
one to catch the fact that there are more possible matching errors that
exist which must be handled accordingly

In the previous commit I have a test which is broken partially because
it is and partially because it is the wrong test. This is fixed in this
commit. As well as another test which discovered during development.

After adding some failing test cases I made the necessary changes to get
it working now some refactor

I have always undetstood passing booleans into functions to be a
codesmell so instead of calling `FindMatch` with the isLoose flag I have
opted to call two different functions bassed on weather the isLoose flag
is set. This chould be taken one step further and be made part of the
`CallSet` itself but was not sure if that abstraction made sense

After some further dive down I have realized that After does not work in
LooseMode assuming we want to maintain a close to exact feature set I
have added a test to demonstrate this failing behavior. Fix to come.

weather a calls prereqs are met doesn't seem semntically signifigant to
weather it is a match so I removed that as a dependancy and now call it
in the `callSet`s `FindMatch` methods which allows each version to
decide if that is necessary. This change enables us to fix the fact
that `After` does not work with LooseMode