Remove ContainsTarget on onenotePage navigation properties

[MIchaelMainer]

Closes #25

C# Generation

Generation for navigation properties to a single entity (not in a collection) appears to be setup well. By removing ContainsTarget for this scenario, the existing method call pattern will stay the same:

client.Users[""].Onenote.Pages[""].Request().Expand(x => x.ParentSection).GetAsync();

The difference is that it will be technically a breaking change as client.Users[""].Onenote.Pages[""] will change from returning an IOnenotePageRequestBuilder to a IOnenotePageWithReferencesRequestBuilder. IOnenotePageWithReferenceRequestBuilder enables client.Users[""].Onenote.Pages[""].Reference.Request() which has DeleteAsync() for removing references and PutAsync(string) for adding references. GetAsync(), CreateAsync(), DeleteAsync(), and UpdateAsync() are still available from client.Users[""].Onenote.Pages[""].Request() with this change.

Quick dump. We have an issue when this type of change happens when we remove ContainsTarget=true from navigation properties of collections.

Java generation

TBD