Fixed #13495 added setting for name order

[snipe]

This should fix #13495, where a Korean user mentioned that in Korea, names are displayed last name first. This adds a setting in Settings > Localization that will let the admin decide whether names should be presented last name first or first name first. I also found a method that I don't think we use anymore.

[what-the-diff]

PR Summary

• Modification to Settings Controller
  This change helps to store the preferred user name display format in the settings.

• Adjustment in Users Transformer
  Now, the system is utilizing the getFullNameAttribute() method to generate the full name of users, empowering flexibility in the name display format.

• Update in User Model
  Improved the getFullNameAttribute() method to return names based on the preferred display format stored in the settings.

• UserPresenter Adjustment
  The system now uses the getFullNameAttribute() method instead of the fullName() method for better naming consistency.

• Database Migration
  Introduced a new column name_display_format in the settings table, allowing a place to store users' name display preferences.

• Translation String Additions
  Addition of new translation strings to potentially enhance international user experience with custom name display formats.

• Form Macro Update
  Introduced the Form::name_display_format macro for enhanced name form creation and easier utilization.

• UI Changes in Account Profile and Default Layout
  Adjustments were made to the layout of the language selection dropdown and the name display in the dropdown menu for logged-in users to make it more user friendly.

• Addition in Settings View
  Added a field for name display format preference in the settings view allowing users to change the name display format as per their preference.

[spencerrlongg]

Looks good!

[marcusmoore]

A couple minor notes but nothing to hold this back. Looks good 😄

[marcusmoore]

I'm sure you already know this but because this is an accessor on the user model we can do $user->full_name instead of having to call the method.

Is calling the method an intentional pattern that I should start following?

[snipe]

I'm not sure what you mean here?

[marcusmoore]

The get*Attribute() syntax tells Laravel to allow it to be accessed like a "normal" property so you could do $user->full_name.

I'm 99% sure there is no benefit doing it that way but I normally don't see the full get*Attribute() call in code.