Small UX improvements to the SAST Configuration UI

Problem to Solve

There are a few inconsistencies on the SAST Configuration UI page that need small updates.

Proposal

Current	Change to
In the expandable SAST Analyzers section, Bandit comes after Brakeman. Alphabetically, Bandit should be listed first.	Move Bandit to the top of the list, then Brakeman (then ESLint, etc)
Inconsistencies with periods (.) in the SAST analyzer variable titles.	Both the periods in Brakeman confidence level. and the one under Bandit: Paths to exclude from scan. should be removed.
All analyzer names are capitalized except kubesec.	Change kubesec to Kubesec
We're using 2 different names for Gosec. For some reason, under the analyzer names, we use Golang Security Checker and then Gosec in the variable title below it. Lucas wasn't sure where Golang Security Checker came from.	Change Golang Security Checker to Gosec