adding missing RIDs

[mairaw]

Fixes #829, #923

Pending questions:

• Windows AOT RIDs: these are for .NET Native. Should I add them to the docs?

/cc @richlander @blackdwarf

[svick]

Should this say "macOS" per #612 (comment)?

[mairaw]

what do you think @richlander? Should we keep OS X as you suggested back in that earlier comment? I was following how we're calling the OSes on this page for this change: https://www.microsoft.com/net/core

[mairaw]

Updated the doc based on comments from @piotrpMSFT and @ericstj. Thanks guys!

There's still a question on whether we want to list the AOT RIDs at this point or not, but this is ready for review if we don't.

/cc @blackdwarf

[thesmithee]

@ericstj are AOT RIDs targetable?

[ericstj]

What do you mean by targetable? No RIDs are "targetable" today because NuGet doesn't allow for different compile time assemblies based on RID (what we typically refer to when we say targetable). RIDs control what runtime assemblies are used. We do indeed use the aot RIDs for UWP applications when that application is using the .NETNative toolchain.

[mairaw]

@ericstj so I should add them here to this doc too? Can people use that in their json files already in their .NET Core projects?

[ericstj]

Not for .NET Core, only UWP.

[thesmithee]

@ericstj I meant are they "usable" for a, for instance, self-contained deployment, to which you gave an answer above. OK, so since these are .NET Core docs, I would suggest not putting them in and keeping with those we can use in .NET Core projects.

[mairaw]

Yes, I agree with this plan @blackdwarf. And what about the changes? Do they look OK to you?

[thesmithee]