Fix handling of the consolidate-redundant-resources modification that goes live Dec 6

[justincy]

When the consolidate-redundant-resources is live it returns a 303 redirect from Person With Relationships, Spouse Relationships, Child Relationships, Parent Relationships, Source References, Discussion References, and Memory References. 3xx redirects have always been problematic for the SDK because Chrome doesn't copy all portions of the original request include the Accept header so on the subsequent request the API defaults to an XML response.

The good news is we can add the X-Expect-Override header on requests to those resources and manually handle the redirect. We will publish a new version of the SDK ASAP that does this.

The bad news is when the pending modification is permanently activated on Dec 6, all old versions of the SDK will not be able to handle requests to any of the deprecated resources. I think.

[justincy]

List of deprecated SDK methods:

• getPersonWithRelationships()
• Person.getSpouseRelationships()
• Person.getParentRelationships()
• Person.getChildRelationships()
• getSourceRefs()
• Person.getSourceRefs()
• ChildAndParents.getSourceRefs()
• Couple.getSourceRefs()
• getPersonDiscussionRefs()
• Person.getDiscussionRefs()
• getMemoryPersonaRefs()