Improve development info: publishing process / push.chocolatey.org

[andreashaerter]

DEVELOPMENT.md should be extended with more information about

• additional information how to prepare the repo:
  • .nuspec version-tag
  • .nuspec releaseNotes tag if not pointing to CHANGELOG.md
• how to release a package and push to https://push.chocolatey.org/
• what to expect after submitting:
  • automated emails will give you up2date information about how to reach a human if needed.
  • If one has fixes, repushing the package with the exact same version is possible (unless the change we requested was based on an incorrect version)
    • This is allowed until approved.
    • Therefore, the currently described release preparation on the repo (tagging, than nuspec pushing) should be adopted. I think tagging a commit and pushing it to Github makes sense only after the it is certain that it matches the push.chocolatey.org version, including fixes which where re-pushed to push.chocolatey.org with the exact same version number.