Added Ldap Company as option and FMCS Notification

[Godmartinz]

Description

This adds ldap_company to the settings table as a syncable option for LDAP.

This also adds an addition to the notification system, if FMCS is turned on it will notify you in the Navbar with info on the Asset/License/Accessory in question.

Notifications are links to the item/s in question.
https://github.com/snipe/snipe-it/assets/47435081/5d10fcba-6f87-4d58-bd62-5ee56d667e49
The notification logic does not fire unless FMCS is turned on.
https://github.com/snipe/snipe-it/assets/47435081/bb5a227a-55ea-48f0-aae2-553830815800

Fixes # [sc-25411]

Type of change

Please delete options that are not relevant.

• [ x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[what-the-diff]

PR Summary

• Addition of a New LDAP Company Sync Functionality
  The update introduces a new variable ($ldap_result_company) in the LdapSync.php file which allows the application to handle the 'company' field pulled from the LDAP data. This variable plays a key role in enhancing how user data is synchronized from LDAP servers to our application.

• Ensuring Consistency of New LDAP Field Across Files
  The ldap_company field has been added to SettingsController.php and Setting.php files. This is vital in keeping the application's settings consistent throughout the application and making sure that the new field is recognized and managed properly in the system.

• Update of Language File for New LDAP Field
  The general.php language file has received an update which now includes the ldap_company field. This change ensures the new field is understood and displayed correctly in the context of the application's localization and internationalization.

• Integration of New LDAP Field in Templates
  Finally, the ldap_company field has been added to the ldap.blade.php template file. This addition ensures that the new 'company' attribute from LDAP is distributed as per the user interface design, hence improving the user's visual experience.

[snipe]

What happens if the user already had things checked out to them that belong to a certain company, and then the user's company changes with FMCS turned on?

[snipe]

A few questions we need to think through, I think?

[snipe]

Can you handle these merge conflicts when you get a moment?

[Godmartinz]

conflicts handled 👍

[snipe]

Hm, some tests are failing that are related to the accessories stuff - I think maybe the develop merge bonked something?

[snipe]

@Godmartinz awesome, thanks - can we get those tests passing?

[Godmartinz]

So a new Accessory_Checkout model had been introduced, I fixed the the relationships and the method calls for accessories. Still have to fix up the asset relations it seems. working on it 👍

[snipe]

Interesting that tests pass on sqlite.