farming rpc test

[zqhxuyuan]

Description

not add to manta CI yet, as run test suites not opened for now:
This rpc testcase only for manta runtime.

---

Before we can approve this PR for merge, please make sure that all the following items have been checked off:

• Connected to an issue with discussion and accepted design using zenhub "Connect issue" button below
• Added one label out of the L- group to this PR
• Added one or more labels from the A- and C- groups to this PR
• Explicitly labelled A-calamari and/or A-manta if your changes are meant for/impact either of these (CI depends on it)
• Re-reviewed Files changed in the Github PR explorer.

Situational Notes:

• If adding functionality, write unit tests!
• If importing a new pallet, choose a proper module index for it, and allow it in BaseFilter. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.
• If needed, update our Javascript/Typescript APIs. These APIs are officially used by exchanges or community developers.
• If modifying existing runtime storage items, make sure to implement storage migrations for the runtime and test them with try-runtime. This includes migrations inherited from upstream changes, and you can search the diffs for modifications of #[pallet::storage] items to check for any.

[github-actions]

✅ Congestion test: 1-day congestion cost (manta-runtime) is above the target daily congestion cost

[github-actions]

⚠️ Congestion test: 1-day congestion cost (calamari-runtime) is NOT above the target daily congestion cost

[ghzlatarev]

Can't we make the test run for custom/custom asset pair instead of the native/custom pair.
Then we can have it run for Calamari as well ?

Btw ill open a PR to uncomment the rpc correctness and performance test you mentioned in the description - #1221

[ferrell-code]

looks good but seems that ci is failing

[Dengjianping]

Seems mantapay rpc tests didn't get passed.

[ghzlatarev]

Seems mantapay rpc tests didn't get passed.

They rely on starting from a clean state, that's why they should be first.

[zqhxuyuan]

Seems mantapay rpc tests didn't get passed.

They rely on starting from a clean state, that's why they should be first.

Ah, But I have this timeout issue when put farming test after manta pay test.

https://github.com/Manta-Network/Manta/actions/runs/5595302834/jobs/10231502632

[ghzlatarev]

Seems mantapay rpc tests didn't get passed.

They rely on starting from a clean state, that's why they should be first.

Ah, But I have this timeout issue when put farming test after manta pay test.

https://github.com/Manta-Network/Manta/actions/runs/5595302834/jobs/10231502632

It seems it hangs up on this loop after the first attempt to execute a runtime upgrade https://github.com/Manta-Network/Manta/blob/farming_rpc_test/tests/test-farming.ts#L136-L139
I suppose the rpc correctness/performance tests could be messing up the state, as they simply call set_storage with junk data.
The easiest fix would be to split them into their own job like the stress test ones, or run them with the stress test. But that has some assets already registered from 8-17