Chocolatey package structure update

[vlukash]

Keep content and structure in sync for Chocolatey and NuGet packages.

Currently the nuget/dotnetcore/chocolatey/fake.nupkg is generated based on the nuget\dotnetcore\Fake.netcore\win7-x86, which is wrong

Changing the source to .build folder, the same as for NuGet generation.

Chocolatey structure changes:

• use tools folder instead of bin

Targets changes:

• CreateChocolateyPackage - new, use instead of DotnetCoreCreateChocolateyPackage
• PushChocolateyPackage - new, use instead of DotnetCorePushChocolateyPackage
• DotnetCoreCreateChocolateyPackage - removed
• DotnetCorePushChocolateyPackage - removed

[matthid]

I think this works because it moves the nupkg into a different folder. Can you please explain why we need the bin -> tools folder name change within the package? Did you test if this actually works with choco?

[vlukash]

Seems like it's not important to change bin -> tools in this case.
It works with the current structure well.

Originally this PR was created to address an issue with Chocolatey caching but that issue is not relevant anymore.
So I can revert bin->tools change.

Did you test if this actually works with choco?
yes, I've installed FAKE from local nupkg and it worked out:
choco install fake -s fake.nupkg

If we want to use the same *.dlls in Chocolatey as NuGet uses then we can keep this PR.

But if using *.dlls from dotnet core is not an issue then this PR should be deleted and no changes needed.

[matthid]

Yes I agree, we don't need a shared nuget/choco package. So if somebody has the same problem the solution is updating chocolatey...