Add location recording to all macros.

[dmaclach]

For large CI systems it can be costly to generate debug information.
Recording location data for all of the stub/expect/reject macros makes
it a lot easier to record/find failures.

Also renames location to ocm_location to avoid conflicts with objects that we are mocking that already have a location/setLocation method.

[tzvist]

Please take my comments with a grain of salt because I am not very familiar with this code base.

[dmaclach]

Can you give me an outline of how that would work?

[tzvist]

I would prefer that we would assert that the received object isKindOfClass OCMockObject in beginStubMacro/beginExpectMacro/beginRejectMacro(and this way give a much more informative message and have a proper stack trace)

[dmaclach]

Sorry tzvist, could you clarify which received object are you talking about? If it's what I think you are saying, we don't have that info in the begin*Macro method.

[tzvist]

After looking at it some more I have misunderstand the way OCMock finds the class that is stubbed, apparently my proposal would not work.

[dmaclach]

Can you give me an outline of how that would work?

[dmaclach]

Removed the references to self from OCMStub, OCMExpect and OCMReject because it caused a couple of issues:

1. Some set up code was in C functions that didn't have a self to reference
2. It caused potential retain loop warnings/issues for calls that were made in blocks
3. It wasn't being used by the code anyhow, and nil is a perfectly fine value for it.