fix: define range of near-api-js versions as peerDependency instead of an exact one

[denbite]

This PR addresses the problem that occurs when installing dependencies over npm, particularly in the case of using another version of near-api-js, which npm believes isn't compatible according to a version specified in peerDependencies

Example

{
  "name": "guest-book",
  "version": "1.0.0",
  "private": true,
  "engines": {
    "node": ">=18"
  },
  "dependencies": {
    "@near-wallet-selector/bitte-wallet": "^8.9.15",
    "@near-wallet-selector/core": "^8.9.15",
    "@near-wallet-selector/here-wallet": "^8.9.15",
    "@near-wallet-selector/meteor-wallet": "^8.9.15",
    "@near-wallet-selector/mintbase-wallet": "^8.9.15",
    "@near-wallet-selector/modal-ui": "^8.9.15",
    "@near-wallet-selector/my-near-wallet": "^8.9.15",
    "near-api-js": "^5.0.1",
    "next": "14.2.5",
    "react": "^18",
    "react-dom": "^18"
  }
}

The package above is going to fail while installing dependencies with the following error

Additional Info

The problem doesn't seem to occur while using yarn, or pnpm, at least the error message doesn't appear.
npm version is 10.8.2

[gtsonevv]

Hey @denbite, create the PR against the dev branch, please.

The base branch was changed.

[gagdiez]

@gtsonevv I changed the target branch

[denbite]

@gtsonevv I merged this into dev branch, but releases seem to happen only from main branch
do you have an ETA for when it's going to be released?