[Enhancement] (FE Code Style) step2: turn on name and error-prone way of writing check

[morrySnow]

Search before asking

• I had searched in the issues and found no similar issues.

Description

this step need to mod and review seriously since could change code logical.

Solution

Step 2: (241 files, 962 lines (with Step 1))

1. Set below rules' severity to error in Checkstyle, all rules are import to make sure the code is correct
   a. Need Braces
   b. Equals Hash Code
   c. Missing Switch Default
   d. Fall Through
   e. No Finalizer

2. Set below rules' severity to error in Checkstyle, all rules are about name
   a. Member Name
   b. Constant Name
   c. Parameter Name
   d. LambdaParameterName
   e. Local Variable Name
   f. Class Type Parameter Name
   g. Static Variable Name
   h. Method Name
   j. Abbreviation As Word In Name

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct