Chore: update release script for new website repo

[kaicataldo]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain: Update release script

What changes did you make? (Give an overview)
refs eslint/archive-website#576

This updates the release script now that we've change the website repository name to eslint/website.

Is there anything you'd like reviewers to focus on?

I've already changed the repository name, turned off publishing to GitHub Pages, and have updated the Jenkins script. Did I miss anything?

[platinumazure]

LGTM, thanks.

Do we want to maybe use a name like "eslint-website"? It could be a pain if someone has their own "website" repo in their GitHub project directory. It's not a problem for me, at least.

[kaicataldo]

That’s an interesting point. Do you mean to rename the repository or just the name of the directory when we clone it in the release script? My inclination is that it’s probably fine as is since the releases are mostly run in Jenkins, but I don’t have a strong opinion and am happy to change it if others are concerned!

[mysticatea]

I think that we should move the script to eslint/website repo. Because eslint/website repo depends on eslint package, it can update the website without sibling directories.

[kaicataldo]

@mysticatea That sounds good to me. How do you feel about landing this first (just to make sure we’re not blocking the upcoming release)?

[mysticatea]

👍

[kaicataldo]

As a side benefit, if we run the eslint release first and then run the site generation afterwards, we can also bundle eslint and espree in eslint/website as well.