Use weights from recent benchmark

[justinfrevert]

Overview

Integrates weights from recent benchmark run on validator spec machine.

🗹 TODO before merging

• Ready

📌 Submission Checklist

• All commits are signed off (git commit -s) for the DCO
• Changes are backward-compatible (or flagged if breaking)
• Pull request description explains why the change is needed
• Self-reviewed the diff
• I have included a change file, or skipped for this reason:
• If the changes introduce a new feature, I have bumped the node minor version
• Update documentation (if relevant)
• Updated AGENTS.md if build commands, architecture, or workflows changed
• No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

• Additional tests are provided (if possible)

🔱 Fork Strategy

• Node Runtime Update
• Node Client Update
• Other:
• N/A

Links

[Klapeyron]

I am thinking if there will be additional value if we will benchmark with https://crates.io/crates/frame-omni-bencher.
Also side topic, while ago we added hwbench probe #1394 based on https://github.com/paritytech/polkadot-sdk/blob/master/substrate/utils/frame/benchmarking-cli/src/machine/reference_hardware.json & https://github.com/paritytech/polkadot-sdk/blob/bcd139f350ac253b4cc0409993e1d070c4bcc396/substrate/utils/frame/benchmarking-cli/src/machine/hardware.rs#L27, I am thinking if there will be also a value if we will create our own profile based on our own reference hardware

[Klapeyron]

we have twice pallet_collective and pallet_membership for council and technical_committee separately, do we need both?