GHA for detecting whether transaction version bump is required

[ghzlatarev]

-The transaction version must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. If this number is updated, then the spec_version must also be updated.
-This is very hard to determine manually as we're depending on so many pallets from substrate.
-So we should create a GHA to automate the process. The best way to do this is to compare the metadata before and after the changes. Parity has already implemented this so use for reference --> paritytech/polkadot#3631