Move block rate and log limit into toml config

[ferglor]

https://smartcontract-it.atlassian.net/browse/AUTO-10027

In this PR, we are:

• Specifying defaults for the automation block rate and log limit in the toml config, based on the existing hard coded values here
• Cleaning up the old hard coded defaults
• Updating the oc2 config types in code to supply these new values

The configuration values are as follows:

Block rate

• For arbitrum we specify a block rate of 4
• For all other supported chains, we specify a block rate of 1

Log limit

• For eth we specify a log limit of 20
• For optimism, BSC, polygon, avax, and base we specify a log limit of 5
• For all other supported chains, we specify a log limit of 2

Open questions

• Not sure if all the chains I've added defaults for are still supported - is there a list of currently supported chains?

[github-actions[bot]]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production[bot]]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube