Change step with new_cop command for rubocop-rspec

[ydah]

before:

Do 4 steps:
  1. Modify the description of RSpec/CopName in config/default.yml
  2. Implement your new cop in the generated file!
  3. Commit your new cop with a message such as
     e.g. "Add new `RSpec/CopName` cop"
  4. Run `bundle exec rake changelog:new` to generate a changelog entry

after:

Do 4 steps:
  1. Modify the description of RSpec/CopName in config/default.yml
  2. Implement your new cop in the generated file!
  3. Add an entry about new cop to CHANGELOG.md
  4. Commit your new cop with a message such as
     e.g. "Add new `RSpec/CopName` cop"

---

Before submitting the PR make sure the following are checked:

• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• [-] Added tests.
• [-] Updated documentation.
• [-] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
• The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

[pirj]

4 and 3 feel out of order. For our parent project it’s justifiable, they need the pr number in the changelog entry? For us, changelog can be added first if you follow the changelog-driven development approach 😅

[ydah]

That's true. Well, I don't think it's going to be a big problem, especially if the order goes back and forth, so I switched 3 and 4.

[pirj]

Thanks!