Fixes for requiredness indicator in UI

[snipe]

This should fix a regression introduced in #15552, where the requiredness wasn't consistently indicated anymore since switched from a regular class to a pseudo class.

@Godmartinz One thing I noticed here was that we're not accounting for textareas in the CSS. We should probably add that at some point to keep things consistent.

There were a few places where I just pulled the check, since it would never be true.

[what-the-diff]

PR Summary

• Increased visibility of required fields
  Border thickness around required input and selection elements in the user interface has been increased, which will make it easier for users to identify mandatory fields.

• Enhancement of multiple-selection
  Improved styling for multiple-selection fields in forms has been introduced, which will provide a better user experience.

• Updates to Blade template files
  Amendments have been made to the layout of these files, enhancing the clarity of the code and facilitating future development work.

• Consistency in required field identification
  The marking method for required fields has been standardized across different parts of the system, providing a more consistent user experience.

• Refinement of the checkout form
  An asset selection element has been added to the checkout form in order to facilitate the selection of multiple assets at once.

• Improvement of form structure
  Redundant class and attribute logic has been reduced, and Bootstrap grid system usage has been standardized, which will benefit overall performance and readability of code.

• Enhancement of accessibility
  Required fields are now clearly marked in both the field label and input tag, allowing users to easily identify necessary fields.

• Removal of unnecessary checks
  Superfluous checks for required class in form groups have been removed from some files, optimizing the system efficiency.

• Simplified error handling
  The process of handling errors for input fields has been streamlined, which will improve speed and usability.

• Consolidation of code practices
  Minor syntax corrections have been carried out to ensure consistency and adherence to best practices in coding.