Remove contracts not getting deployed on outposts and some code cleanup

[ahmadkaouk]

• Remove the contracts that won't be deployed on outposts. (mars-council, mars-red-bank-closure, mars-staking, mars-treasury, mars-vesting, mars-xmars-token)
• Update build settings
• Remove Astroport, Stader and Lido dependencies and related code.
• Disable the compilation of the smart contracts temporarily.

[larry0x]

i think we should include all authors who have contributed to the code base:

authors = [
  "Ahmad Kaouk <ahmad@delphilabs.io",
  "Spike Spiegel <spikeonmars@protonmail.com>",
  "larry_0x <larry@delphidigital.io>",
  "Piotr Babel",
  "Harry Scholes"
]

[larry0x]

@ahmadkaouk added comments regarding Cargo.toml but otherwise lgtm

[grod220]

I wonder if it would be easier to start from a blank slate and adding in features one-by-one (with passing builds). I'm doing this with fields. Otherwise, you may not get a passing build for a looooong time.

[dancreee]

Don't think we should have any chain specific tokens mentioned in core codebase (I know I put it there! :P )

[ahmadkaouk]

True, I will remove this in the next PR.

[dancreee]

while we can remove this swap for now - we'll have to still have some swap logic in here - we need to to probably have this swap asset set as a config item on the protocol_rewards_collector contract, so anyone can still initiate the message but it's the config that stores what asset it will be swapped into (as each change might/will be different)

[dancreee]

We will have a story around the protocol rewards collector refactor where we can add this back in

[dancreee]

I wonder if it would be easier to start from a blank slate and adding in features one-by-one (with passing builds). I'm doing this with fields. Otherwise, you may not get a passing build for a looooong time.

Yea, this is a tough one...

What this way gives us, is a way to easily diff the changes from terra -> osmosis, so it's easy to see what has changed... however it's also very message with just deleting a bunch of stuff etc and there as so many intertwined dependencies that it's hard to migrate each contract across independently...

On the other hand, starting from scratch will take longer and will mean we have to audit/review more code overall, i'm on the fence as to which one is better - we know it can be more or less migrated as we have a PoC doing so already

[ahmadkaouk]

I wonder if it would be easier to start from a blank slate and adding in features one-by-one (with passing builds). I'm doing this with fields. Otherwise, you may not get a passing build for a looooong time.

Yea, this is a tough one...

What this way gives us, is a way to easily diff the changes from terra -> osmosis, so it's easy to see what has changed... however it's also very message with just deleting a bunch of stuff etc and there as so many intertwined dependencies that it's hard to migrate each contract across independently...

On the other hand, starting from scratch will take longer and will mean we have to audit/review more code overall, i'm on the fence as to which one is better - we know it can be more or less migrated as we have a PoC doing so already

Yea, so as @dancreee mentioned, this way make it easier to track changes (diff from the original mars-core repo). To overcome the problem of builds, I disabled the build of the smart contracts temporarily, so I could still be able to test for a passing build and run unit tests after each change. I'll progressively re-enable the build of each contract after finishing its migration.