Update branding for 17.0

[ladipro]

Context

Mainline development is switching to Visual Studio 17.0.

Changes Made

Merging current vs17.0 branch into main to pick up branding changes.

Testing

Grepped the tree for other occurrences of 16.10.

Notes

[ladipro]

There is a possibility we will still need to service 16.10, although it's not LTS so not mentioning it here.

[rainersigwald]

Should we merge the vs17.0 branch back into main first?

In my head we should do these things, in either order

1. Merge Update Visual Studio Version to 17.0 #6361 (maybe with the readme change here added?)
2. Merge vs17.0 to main

I don't think cherry-picking is the right move since we should have clean merges.

[ladipro]

Merging vs17.0 yields the exact same diff as cherry-picking that one commit. Git-sanity wise it's better to merge, that's a good point.

[Forgind]

I think 1 should go first. It should have been a part of the branding in the first place—it wouldn't make sense to have even a build that's partway between dev16 and dev17.

[ladipro]

@Forgind I am planning to delete vs17.0 to prevent confusion - main is going to be 17.0 and vs17.0 would be "16.10 with 17.0 branding" which isn't useful. So I was thinking about taking these steps:

1. Merge this PR. The diff is a traditional branding update that's done after cutting a release branch. The reason I am annoyingly insisting on doing that is that it fits the established pattern.
2. Delete the vs17.0 branch.
3. Repoint Update Visual Studio Version to 17.0 #6361 to main and merge. Update Visual Studio Version to 17.0 #6361 is a major version branding update so it's great that it has its own PR.

EDIT: There's actually step 0. Merge #6409 so main history goes nicely from 16.10 to 16.11 to 17.0.

[rainersigwald]

Works for me

[Forgind]

Is there any reason we have to delete vs17.0? We've created vs16.x branches before they're really properly full before. Are we just going slower here because we have so long before 17.0 ships?

Also, are we then planning to have main insert into VS main and rel/d17, or are we planning to abandon rel/d17?

[ladipro]

No strong reason to delete, it's just not needed until the next snap. VS rel/d17 is also sitting unused until the next preview. We'll be inserting our main into VS main for a few months, ignoring the "17" branches on both ends.

It's a good analogy, though. I'm not deleting and will keep the branch around. Thank you!