[Astar] Integrate `tx-pause` & `safe mode`

[ipapandinas]

Follow-up on #1364 for the Astar runtime.

SafeMode Config

• ForceEnterOrigin: EnsureRootOrTwoThirdsTechnicalCommittee
• ForceExtendOrigin: EnsureRootOrTwoThirdsTechnicalCommittee
• ForceExitOrigin: EnsureRootOrAllTechnicalCommittee

TxPause Config

• PauseOrigin: EnsureRootOrTwoThirdsTechnicalCommittee
• UnpauseOrigin: EnsureRootOrTwoThirdsTechnicalCommittee

TODO

• Docs update

[ipapandinas]

Still relevant, but we have to define parameter values by having the following in mind:

• How long can recovery operations last following an incident?
• Rules for entering/exiting (roles, durations, delays, whitelisting) - Should be aligned with governance parameters

[Dinonard]

@ipapandinas about the XCM e2e tests, what do you mean?

[ipapandinas]

@Dinonard From what I recall, I wanted to ensure that received XCM programs are not processed in safe mode or when polkadotXcm calls are paused.

[Dinonard]

I see, thanks for the reply.

polkadotXcm pause shouldn't have any effect on the XCM processing though since we can only block extrinsic calls.
For general XCM execution, once origin is derived (and it's non-root), call filter is still applied to every call so it doesn't make a difference.

[ipapandinas]

Yes, it's not relevant to test, I've updated the issue summary, thanks!