Feat: Add Injective Proto Paths Using Build Flags

[maxrobot]

Description

In this PR the following changes are made:

• Update the optimizer version to 0.16.1
• Update the protos to support Injective tokenfactory
• Change the type of igp to Uint128 as u128 is no longer supported.
• Ignore tests that don't work (note I think the ethereum ABIs are outdated...)
• Added labels to contracts in tests as None is not supported in some minor version that is being pulled (hence Cargo.lock)

Now when the optimizer is run it creates two binaries for the warp native contract:

• Osmosis: with the standard tokenfactory proto path
• Injective: with the injective tokenfactory proto path

Everything else is the same.

Note:

Please commit the Cargo.lock in future as I think it will make it easier for others to successfully build and run the tests.

[yorhodes]

were these just undocumented? I dont see them referenced in this PR

[maxrobot]

If you try to run the make scripts and don't have these then it fails:

optimize-fast:
	cargo cw-optimizoor
	rename --force 's/(.*)-(.*)\.wasm/$$1\.wasm/d' artifacts/*

and if you haven't install foundry then the wasm integrations tests don't work as it needs anvil...

[yorhodes]

should these changes be reverted?

[maxrobot]

So if you don't have these defined and run optimize-fast the tests fail.

[yorhodes]

curious why this was necessary
we use u128 elsewhere too

[maxrobot]

If you take a clean repo and run the tests you will notice this will fail.

This is an issue because you didn't commit Cargo.lock so all the dependencies will pull the latest patch version.

[yorhodes]

looks mostly good to me although maybe could have just had the feature flag affect the URL prefix