[pr] Serialize structs for svm-rollup module

[DudessaPr]

Problem

Some structs have to be Serializable to be included in SVM module in svm-rollup repository

Summary of Changes

Serialized ComputeBudget, FeatureSet, FeeStructure and FeeBin (which is within FeeStructure)

Fixes #

[Yiwen-Gao]

There are some structs that we also duplicate in svm-rollup and apply serialization macros to. Do you have a system for which structs get modified in our Agave fork VS which are duplicated in svm-rollup?

[DudessaPr]

There are some structs that we also duplicate in svm-rollup and apply serialization macros to. Do you have a system for which structs get modified in our Agave fork VS which are duplicated in svm-rollup?

For FeatureSetWrapper in SvmPrevConfig, we can use just FeatureSet and serialize it in agave now. Walter made that wrapper because we tried to not change Agave's code that time. About FeeRateGovernorWrapper, FeeRateGovernor has one field marked as serde-ignore that nullifies the value when the struct it cloned, and it is bad in our case when working with sovereign modules as they clone objects into sov-state. I do not really know what's the purpose of that serde-ignore therefore I created a Wrapper for that struct to be safe.

[Yiwen-Gao]

Got it, thanks for explaining. It sounds like we're going to modify the types in Agave directly moving forward. Feel free to make a follow-up PR to remove those types from svm-rollup and update Agave accordingly.

I agree that we should leave FeeRateGovernor alone and can leave that one type in svm-rollup.