Removed unused files in assets directory

[marcusmoore]

Description

This PR removes unreferenced files from the /resources/assets/ directory. These files are all sourced from third party libraries and were either copy/pasted from node_modules or from GitHub and added to version control.

"unreferenced" means they are not being referenced in our webpack.mix.js file and their removal doesn't cause any build errors.

Type of change

Please delete options that are not relevant.

• Let's call it "repository clean up"

[shortcut-integration]

This pull request has been linked to Shortcut Story #24353: Remove files from resources/assets/* that are not being used in webpack.

[what-the-diff]

PR Summary

• Removal of Component Styling Files
  The team has deleted several CSS files that were responsible for styling various components (ex: tables, date pickers, wysiwyg editor). This means the look and feel of these components might change.

• Removal of Font Files
  Several files that provided font resources for FontStyle icons have been removed from our system. This means we might see some changes in the icons used within the application.

• Deletion of Locale Files for Bootstrap Table
  Numerous locale files for a Bootstrap table component were deleted. These files contained translations for the component in several different languages.

• Deletion of Scripts
  Some JavaScript files (dashboard.js, dashboard2.js, bootstrap-table-cookie.min.js, and others) have been removed. These scripts could have had various functionalities in our application, so we might notice some changes in our app's behavior.

• Removal of LESS Files
  Several LESS files, that determined the styles for various UI elements (like boxes, buttons, headers, navs etc.) have been deleted. This will possibly impact the appearance of these elements in the system.

Please note that these deletions might be part of a broader restructuring or redesign effort. Make sure to check out our latest app version to see the changes in action.

[marcusmoore]

@uberbrady forgot to tag you for a review (since you've been managing the v7 branch)

[marcusmoore]

@snipe I just checked and we're still able to do exports (I checked assets) via the table menu:

[uberbrady]

I made sure to blow out my ./node_modules directory, did a fresh npm install and made sure to make production assets, then click around. Everything seemed to work fine!