Move all imported constants to our code base

[ghzlatarev]

Description

Move constants to our code-base, in order to not have them change without us realizing:

• BlockExecutionWeight
• ExtrinsicBaseWeight
• WEIGHT_PER_SECOND
• BlockHashCount
• RocksDbWeight
• SlowAdjustingFeeUpdate

---

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, A-dolphin 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.

[Dengjianping]

what about this RocksDbWeight in weight files? Maybe you have to update weight template.
https://github.com/Manta-Network/Manta/blob/manta/runtime/calamari/src/weights/calamari_vesting.rs#L43

[ghzlatarev]

They will be regenerated in the release PR, but I can also do it here if you guys want.

[Dengjianping]

They will be regenerated in the release PR, but I can also do it here if you guys want.

Yeah, we can fix it in next release.