chore: error on max-params

[cmwylie19]

Description

There is currently only one maxParams error, should we go ahead and enforce this with an error and then get this #1728 ready to merge with deprecation warnings?

Related Issue

Fixes #

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.12%. Comparing base (f3e40bb) to head (65172f5).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1782   +/-   ##
=======================================
  Coverage   82.12%   82.12%           
=======================================
  Files          52       52           
  Lines        2215     2215           
  Branches      436      470   +34     
=======================================
  Hits         1819     1819           
+ Misses        394      367   -27     
- Partials        2       29   +27     

see 7 files with indirect coverage changes

[samayer12]

I'm okay with enforcing this as an error. If we need to support more params in a function this will force us to have a discussion around function design, which should pay off in the long-run.

[samayer12]

Looks like format is blocked pending #1728

[samayer12]

Now pending #1787