feat: add utility pallet

[cuteolaf]

No description provided.

[ndkazu]

Is there a reason for not adding "pallet-utility/try-runtime" here?
and there is also the missing "pallet-utility/runtime-benchmarks" in the runtime-benchmark section.
Usually I refer to the following Files/folder to add pallets:
https://github.com/paritytech/substrate/blob/polkadot-v0.9.26/bin/node/runtime/Cargo.toml

I also realise that this rule (adding the pallet in try-runtime and runtime-benchmark) was not always respected in implementation of previous pallets. Let's learn & improve together!!

[ndkazu]

Here also, missing [pallet_utility, Utility] in the define_benchmark section.

[letodunc]

To prevent missing things when adding a new pallet, there is a script that automatize it for you. It's add_new_pallet.sh in the scripts folder. You execute it from the root folder of the project. In your case, a use could be scripts/add_new_pallet.sh utility Utility. Everything will be correctly configured for the basic add in the project. Then you can customize it with what you need.

[ilhanu]

No sure why the coverage tests are failing, might have to do with the that it's an external PR

[codecov-commenter]

Codecov Report

Merging #131 (56526b1) into main (fb5a4e8) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage   73.13%   73.13%           
=======================================
  Files          40       40           
  Lines        2922     2922           
=======================================
  Hits         2137     2137           
  Misses        785      785           

Impacted Files	Coverage Δ
runtime/src/lib.rs	2.38% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ilhanu]

@cuteolaf can you please check the logs for the benchmarking and provide a fix.

[ndkazu]

A few things I do before sending a commit:

1. cargo check to make sure that it compiles (you probably did it already).
2. cargo test to be sure that all the tests are correctly configured and pass.
3. cargo build --release --features runtime-benchmarks to be sure that all the benchmarks are correctly configured and pass.
   sometimes you will also have additionnal tests in your benchmarks (it is the case for some FairSquares pallets), in this case you also want to run the following:
4. cargo test --features runtime-benchmarks

In my experience, If all the checks above pass on your local node, your commit will checkout without ANY problem.