Rename Finality Verifier and Call Dispatch Pallets (#838)

* Rename `pallet-finality-verifier` to `pallet-bridge-grandpa`

* Missed some CamelCase ones

* Update logging target in GRANDPA pallet

* Rename `pallet-bridge-call-dispatch` to `pallet-bridge-dispatch`

* Rename the dispatch pallet folder

* Update logging target in Dispatch pallet

* Missed a couple

* Format the repo

* Stop listing individual pallets in Compose logs

* Use correct pallet name in module doc comments

* Add `pallet-bridge-dispatch` to README project layout

* Sort crate names in TOML files

* Rename `pallet-bridge-grandpa` runtime Call alias

bridges/docs/high-level-overview.md

@@ -131,7 +131,7 @@ require bi-directional header sync (i.e. you can't use message delivery with one
 
 #### Dispatching Messages
 
-The [Message dispatch pallet](../modules/call-dispatch/src/lib.rs) is used to perform the actions
+The [Message dispatch pallet](../modules/dispatch/src/lib.rs) is used to perform the actions
 specified by messages which have come over the bridge. For Substrate-based chains this means
 interpreting the source chain's message as a `Call` on the target chain.
 
@@ -172,6 +172,6 @@ source chain needs to prove ownership of this account by using their target chai
 sign: `(Call, SourceChainAccountId).encode()`. This will be included in the message payload and
 verified by the target chain before dispatch.
 
-See [`CallOrigin` documentation](../modules/call-dispatch/src/lib.rs) for more details.
+See [`CallOrigin` documentation](../modules/dispatch/src/lib.rs) for more details.
 
 #### Message Relayers Strategy