It can be difficult to confirm current spidermon thresholds for monitors

[further-reading]

We recevied from feedback that it is common for users to have difficulty confirming what a spider's current monitor thresholds are. This is due to the myriad ways these can be set:

• In a project's settings.py file.
• In a spider's custom_settings attribute.
• In the project settings tab on the zyte dashboard.
• In the spider settigns tab on the zyte dashboard.

The suggestion we have received is to include logs that state the current thresholds to make it clear to a user what targets the monitors are following.

[further-reading]

After discussing with the maintainer we decided this isn't under spidermon's purview as the root cause is how scrapy handles its settings. I've opted to make a extention to report on settings at runtime which will handle this use case.