chore: make blst portable

[blckngm]

What this PR does / why we need it?

This PR enables the portable feature of the blst crate so that axon won't use ADX instructions.

From blst readme:

If final application crashes with an "illegal instruction" exception [after copying to another system], [...] And if you compile a Rust application, you can pass --features portable to cargo build.

What is the impact of this PR?

No Breaking Change

PR relation:

• This should fix CI may be broken by illegal instruction #1387. Some github runners don't support ADX.

CI Settings

CI Usage

Tip: Check the CI you want to run below, and then comment /run-ci.

CI Switch

• Web3 Compatible Tests
• OCT 1-5 And 12-15
• OCT 6-10
• OCT 11
• OCT 16-19
• v3 Core Tests

CI Description

CI Name	Description
Web3 Compatible Test	Test the Web3 compatibility of Axon
v3 Core Test	Run the compatibility tests provided by Uniswap V3
OCT 1-5 | 6-10 | 11 | 12-15 | 16-19	Run the compatibility tests provided by OpenZeppelin

[blckngm]

Workflow run where the runner doesn't support ADX: https://github.com/axonweb3/axon/actions/runs/6665823425/job/18116195808#step:5:69

[yangby-cryptape]

Sorry, I didn't catch your meaning.

• How did you confirm it was caused by ADX? I didn't find any useful log follow the link you pasted.

  Workflow run where the runner doesn't support ADX: https://github.com/axonweb3/axon/actions/runs/6665823425/job/18116195808#step:5:69

• I didn't find docs about this.

  Some github runners don't support ADX.

I don't try to reject your PR, it's pretty good.

I'm just curious. I think your PR is a good try, but doesn't be proved to be a final solution from that logs.

[blckngm]

Sorry, I didn't catch your meaning.

* How did you confirm it was caused by ADX? I didn't find any useful log follow the link you pasted.
  > Workflow run where the runner doesn't support ADX: https://github.com/axonweb3/axon/actions/runs/6665823425/job/18116195808#step:5:69

See the build axon step: lscpu says the cpu is E5-2673 v3, and it doesn't support ADX (adx is not in the flags). If you look up this CPU on intel website, you'll see it's haswell and indeed doesn't support ADX. ADX is supported since the next generation (broadwell).

[yangby-cryptape]

See the build axon step: lscpu says the cpu is E5-2673 v3 ...

Then, you should paste that link to #step:4:24. 🤓 But you pointed to #step:5:69.

[yangby-cryptape]

Merge CI failed since failures: tests::system_script::metadata::test_write_functions. (ref: #1374 (comment))