chore: refactor procedures namespace

[BeksOmega]

The basics

• I branched from develop
• My pull request is against develop
• My code follows the style guide
• I ran npm run format and npm run lint

The details

Resolves

Fixes #6525

Proposed Changes

Refactors the procedures namespace to use the new procedure block interface methods instead of the old ones.

Should be no change in behavior.

Reason for Changes

Realized I actually did need to refactor this so that external devs don't have to implement the old getProcedureDef and getProcedureCall methods.

Test Coverage

Passes all existing tests.

Documentation

N/A

Additional Information

Dependent on #6736

[gonfunko]

Do we want to mark this as a breaking change? I realize the root blocks are updated to accommodate it, but since the interface changed it might still be worth calling out?

[BeksOmega]

All the changes I made should be backwards compatible (that was my goal anyway). Do you see something I missed?

[gonfunko]

All the changes I made should be backwards compatible (that was my goal anyway). Do you see something I missed?

Just the change to the IProcedureBlock interface; theoretically somebody could have created a class that implements it and doesn't inherit from the core procedure blocks, in which case it would break I think? But I can easily be convinced that's enough of an edge case to not worry about.

[BeksOmega]

All the changes I made should be backwards compatible (that was my goal anyway). Do you see something I missed?

Just the change to the IProcedureBlock interface; theoretically somebody could have created a class that implements it and doesn't inherit from the core procedure blocks, in which case it would break I think? But I can easily be convinced that's enough of an edge case to not worry about.

Ah sweet, that was only released in December, and according to our readme: "Once a new API is merged into master it is considered beta until the following release." so we get away with this one scot-free 😎