chore(deps): update dependency rubocop-on-rbs to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rubocop-on-rbs (changelog)	'~> 1.8' → '~> 2.0'

---

Release Notes

ksss/rubocop-on-rbs (rubocop-on-rbs)

v2.0.0

Compare Source

• Support rbs v4 by @​ksss in #​145
• Drop RBS/Lint/WillSyntaxError by @​ksss in #​145

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile.lock

Writing lockfile to /tmp/renovate/repos/github/poporonnet/mruby_io_types/Gemfile.lock
Fetching gem metadata from https://rubygems.org/...........
Resolving dependencies...

Could not find compatible versions

Because steep >= 1.10.0 depends on rbs ~> 3.9
  and rubocop-on-rbs >= 2.0.0 depends on rbs ~> 4.0,
  steep >= 1.10.0 is incompatible with rubocop-on-rbs >= 2.0.0.
So, because Gemfile depends on rubocop-on-rbs ~> 2.0
  and Gemfile depends on steep ~> 1.10,
  version solving has failed.

[tufusa]

Steep の RBS 4 対応アップデートまで待ち

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.