Generalize test mocks

[aokj4ck]

Description

Subtask of: https://mapbox.atlassian.net/browse/SSDK-557

• Replace MockResponse enum with a MockResponse protocol
• Add an ApiType for every MockResponse instance
• Split previous MockResponse enum into
  1. SBSMockResponse
  2. GeocodingMockResponse
  3. AutofillMockResponse
• Change MockWebServer and XCTestCase-base-classes to have a generic type conforming to MockResponse
  • This allows us to special test cases according to the Mock data and its corresponding ApiType
  • A test case that specializes in GeocodingMockResponse can:
    • Invoke server.setResponse(_ response: Mock) and the generic Mock will be GeocodingMockResponse
    • Query Mock.apiType to retrieve GeocodingMockResponse.apiType which will return .geocoding and instantiate a testable SearchEngine with this value
    • Always convey the ApiType that the tests will use because it's prominently shown in the generic value Mock and available in the strong type inferences.
• Distinguish mock data by the API type so that it is aligned throughout the base class, to the mock server, into the mock data, and into every test.
• Run UI Tests in every PR
• All tests now use mocked data through the Swifter local HTTP server
  • Previously a variety of tests used production api.mapbox.com to query
• Skip OfflineIntegrationTests (for now)

Checklist

• Update CHANGELOG
• Align UI tests by mock
• Rename LegacyResponse to GeocodingMockResponse
• Pare unused cases from Geocoding, SBS mocks

Screenshots

Address Autofill Integration Test

With mixed mocks	With MockResponse generics
Non-generic base TestCase class ApiType is constant in setUp function setResponse(.retrieveAddressSanFrancisco) and .suggestAddressSanFrancisco are of enum type MockResponse and mixed with mocks from all other Api types (geocoding, SBS, future search-box) which can allow misalignments between api types and mock data	Base TestCase class has a generic that conforms to MockResponse. This guarantees that the mock data is typed according to the mock's ApiType and that we can instantiate a SearchEngine using the same ApiType dynamically. The ApiType in setUp function is dynamic and matches the generic MockResponse.apiType setResponse(.retrieveAddressSanFrancisco) and .suggestAddressSanFrancisco are of type AutofillMockResponse so we can use those strongly typed values (see …Address…) that only occur in the AutofillMockResponse enum so we know they are provided from this API, correct for this API, and not confused with any other API

Geocoding Integration Test

With mixed mocks	With MockResponse generics
Non-generic base TestCase class ApiType.SBS is constant in setUp function setResponse(.categoryCafe) is of enum type MockResponse and mixed with mocks from all other Api types (geocoding, autofill, future search-box) which can allow misalignments between api types and mock data	Base TestCase class has a generic of SBSMockResponse that conforms to MockResponse. This guarantees that the mock data is typed according to the mock's ApiType and that we can instantiate a CategorySearchEngine using the same ApiType dynamically. The ApiType in setUpWithError function is dynamic and matches the generic MockResponse.apiType setResponse(.categoryCafe) is of type SBSMockResponse so we can use those strongly typed values that only occur in the SBSMockResponse enum so we know they are provided from this API, correct for this API, and not confused with any other API

[aokj4ck]

Depends on #167 which adds new tests

[OdNairy]

nit: looks like we can remove explicit typealias declaration

[aokj4ck]

That would cause the Test subclasses to need either:

1. declare a name in the generic, such as <Mock: MockResponse> (more noise, but explicit which is nice) or
2. change Mock usages to the default name T, such as T.coreApiType.toSDKType() (more obtuse IMHO)

The typealias is inherited and I think it's the simplest approach (although you do have to visit the parent class definition to find the typealias.) Let me know what you think.

[OdNairy]

LGTM

[ghost]

LGTM overall, although I'm not an expert in iOS stuff :)