As part of the refactoring work in Secret forms, due to possible future PF6 update (The PF6 update will introduce variable name changes across PatternFly, meaning that all existing CSS overrides must be updated), we should be using the PF components in all places, where we have previously used custom and styled <div> components with className attributes or some of the PF CSS overrides. 

Examples of some of the candidates to be replaced are

• add/remove credentials buttons uses some classNames that could be replaced by Buttons icon/iconPosition params
• parse error message could be replaced by error HelperText. 

All components that are being updated as part of this epic should be checked.

AC:

• Identify components that are replaceable by existing PF components
  • Examples of such replaceable components are add/remove credentials buttons or parse error message.
  • As a good candidate of PF components we will be using are HelperText  InputGroup or 
• Update the forms to use PF components, where possible.
  • It is important that we keep the styling aligned between the forms, so when making a PF component change, check if the styling of the subcomponents correspond to each other.