feat: rewards and rewards v2 integration for hello world

[Sidu28]

Routes createAVSRewardsSubmission call via the servicemanager called by the rewardsInitiator vs directly calling it.

[stevennevins]

there is some more updates that I think we need to make this more flexible.
I started addressing some things in #93

we need to add a function with an initializer modifier on the service manager to initialize the owner and rewards updater state variables. this makes it so you don't need to prank(address(0));

these values need to be read from a config file for the hello world deployment

And then we need to improve the core deployment library to set the rewards updater address on the RewardsCoordinator. We can't read this from the config json files in the core contract repo. It looks like it's an address controlled by the person who wrote the script or maybe the pk for it is shared, but it's likely an internal address to eigenlayer and needs to be more configurable or a default anvil key

[Sidu28]

there is some more updates that I think we need to make this more flexible. I started addressing some things in #93

we need to add a function with an initializer modifier on the service manager to initialize the owner and rewards updater state variables. this makes it so you don't need to prank(address(0));

these values need to be read from a config file for the hello world deployment

And then we need to improve the core deployment library to set the rewards updater address on the RewardsCoordinator. We can't read this from the config json files in the core contract repo. It looks like it's an address controlled by the person who wrote the script or maybe the pk for it is shared, but it's likely an internal address to eigenlayer and needs to be more configurable or a default anvil key

To make it more straightforward, should we just hardcode it in the CoreDeploymentLib.sol file to a default anvil key ourselves instead of using the config?

[stevennevins]

Looks good! Can you add a step in the README that runs through after the contracts are deployed is able to go through the payment flow. I realize we missed that on the first pass for this feature

[Sidu28]

@stevennevins wanted to bump this for review