[CELEBORN-2049] Bump Ratis version from 3.1.3 to 3.2.1

[SteNicholas]

What changes were proposed in this pull request?

Bump Ratis version from 3.1.3 to 3.2.1 including adding options of celeborn-ratis sh peer add -peers in celeborn_ratis_shell.md to follow up apache/ratis#1282.

Why are the changes needed?

Bump Ratis version from 3.1.3 to 3.2.1. Ratis has released v3.2.1, of which release note refers to 3.2.1. The 3.2.1 version is a maintenance release with multiple improvements and bugfixes. The usage of celeborn-ratis is as follows:

$ celeborn-ratis sh
Usage: ratis sh [generic options]
	 [election [transfer] [stepDown] [pause] [resume]]         
	 [group [info] [list]]                                     
	 [local [raftMetaConf]]                                    
	 [peer [add] [remove] [setPriority]]                       
	 [snapshot [create]]

$ celeborn-ratis sh election transfer
Usage: transfer -address <HOSTNAME:PORT> -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] [-timeout <TIMEOUT_IN_SECONDS>]

$ celeborn-ratis sh election stepDown
Usage: stepDown -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>]

$ celeborn-ratis sh election pause
Usage: pause -address <HOSTNAME:PORT> -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>]

$ celeborn-ratis sh election resume
Usage: resume -address <HOSTNAME:PORT> -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>]

$ celeborn-ratis sh group info
Usage: info -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>]

$ celeborn-ratis sh group list
Usage: list -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] <[-serverAddress <PEER0_HOST:PEER0_PORT>]|[-peerId <peerId>]>

$ celeborn-ratis sh peer add -peers
Usage: add -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] <[-address <PEER0_HOST:PEER0_PORT>]|[-peerId <peerId>]> [-clientAddress <CLIENT_ADDRESS1,CLIENT_ADDRESS2,...>] [-adminAddress <ADMIN_ADDRESS1,ADMIN_ADDRESS2,...>]

$ celeborn-ratis sh peer remove -peers 
Usage: remove -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] <[-address <PEER0_HOST:PEER0_PORT>]|[-peerId <peerId>]>

$ celeborn-ratis sh peer setPriority
Usage: setPriority -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] -addressPriority <PEER_HOST:PEER_PORT|PRIORITY>

$ celeborn-ratis sh snapshot create
Usage: create -peers <PEER0_HOST:PEER0_PORT,PEER1_HOST:PEER1_PORT,PEER2_HOST:PEER2_PORT> [-groupid <RAFT_GROUP_ID>] [-snapshotTimeout <timeoutInMs>] [-peerId <raftPeerId>]

$ celeborn-ratis sh local raftMetaConf
Usage: raftMetaConf -peers <[P0_ID|]P0_HOST:P0_PORT,[P1_ID|]P1_HOST:P1_PORT,[P2_ID|]P2_HOST:P2_PORT> -path <PARENT_PATH_OF_RAFT_META_CONF>

Does this PR resolve a correctness bug?

No.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

CI.

[SteNicholas]

Merged to main(v0.7.0).