Prepare v4.6.0

[ffoodd]

• Run linters;
• Run compilers;
• Run tests;
• Check documentation site: examples and contents;
• Test cross-browser compatibility locally and with BrowserStack:
• Including RTL mode;
• Ask for reviews and accessibility testing;
• sync with Bootstrap's release and probably wait for it;
• npm run release-version $current_version $next_version to bump version number
  • if bumping a minor or major version:
    • Manually change version_short in package.json
    • Add docs version to _data/docs-versions.yml
    • Manually change docs_version in _config.yml
    • Update redirects in docs frontmatter
    • Move docs to the new docs' subfolder?
    • Ensure Algolia indexes new release content: PR against DocSearch
• npm run release to compile dist, update SRI hashes in doc and package the release
• Prepare changelog:
  • conventional-changelog -p angular -i CHANGELOG.md -s
  • ship list
• commit and push dist with a chore(release) commit message
• merge (on v4-dev for now)
• tag your version, and push your tag
• create a GitHub release:
  • attach zip file
  • paste CHANGELOG in the release's description
• run build/ship.sh x.x.x to…
• publish documentation on gh-pages → ready in chore(release): v4.6.0 #604
  • copy ../bs-docs to the gh-pages branch
  • check every index.html used as redirections to be redirecting to the new release
  • when bumping minor version: ensure dist URLs in examples' HTML has changed
  • double-check everything before pushing, starting by searching for forgotten old version number occurences
• npm pack then npm publish
• publish on Nuget
• check release on NPM, Nuget, Packagist…
• make an announcement in Plazza 🎉