Fix: Set radius connection timeout to monitor default

[chakflying]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Fixes #3185. Untested. If the monitor timeout becomes configurable in the future this can be passed the same variable.

While searching for the documentation of node-radius-client, I found out the repository that npm pointed to has disappeared from public view (https://github.com/w3cj/node-radius-client). IMO this is a pretty bad situation as we will be unable to raise issues if any were found. But there seems to be no alternative to this package so I guess we will have to stick to the status quo.

Type of change

Please delete any options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas
  (including JSDoc for methods)
• My changes generate no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)