Implement changePrizePool correctly

[lordshashank]

current implementation of changePrizePool is not optimal. It just increases the prize pool and that also without updating the prize structs.
Re-implement the function as two functions changePoolPrize and changePrizeArray implementing prize changes for sponsors along with updating the relevant structs.

[yomanthunder]

I would like to solve the issue

[lordshashank]

sure, just make sure to follow the contributing guidlines.

[yomanthunder]

@lordshashank
i have just added one function that was asked to implement in the issue changePrizeArray, but as the contract is very big , Contract code size is exceeding exceeds 24576 bytes (a limit introduced in Spurious Dragon)

what should i do about it ??

[lordshashank]

try to increase optimizer runs to 2000 if it helps.

[lordshashank]

It would not help in long go, comment out the getter functions for public vars as of now (as public vars have their own getter functions) and implement the team functionality. I guess we would have to shift to interfaces for different functionalities, would keep that for another patch.

[yomanthunder]

@lordshashank
I think raising a new issue for the teams functionality will be a good idea
Please do specify how you want to implement the teams feature in that issue

1. Team Structure:
   How should teams be structured and created within the contract?
2. Roles and Permissions:

• What roles do you envision within a team, and what permissions should each role have?

4. Team Interactions:
5. Events and Notifications:

[lordshashank]

The issue is already there #16 , this issue is independent of that, here our aim is to give an option to sponsor to change the prize distribution in main prize and pool prize, this should be pretty straight forward.

[yomanthunder]

@lordshashank, I would greatly appreciate your feedback on my pull request. It's my first contribution, and I'm eager to learn and improve. Please let me know if there are any areas that need attention or if you have any suggestions. Thank you!

[lordshashank]

Resolved here #29