Added console command to encrypt previously unencrypted fields

[snipe]

This is a request from a customer where they have a lot of data in a custom field that they'd like to convert into an encrypted custom field. This is right now just a one-off console command, but I think we can add options to it down the line, and also possibly have it run the reverse way and convert an encrypted field into an unencrypted field.

[shortcut-integration]

This pull request has been linked to Shortcut Story #24971: Ability to convert unencrypted fields to encrypted fields.

[what-the-diff]

PR Summary

• Introduction of New Console Command File
  A new file named 'ToggleCustomfieldEncryption.php' has been added under the 'app/Console/Commands' directory. This new file contains 71 lines of code.

• Implementation of New Console Command
  A new console command 'snipeit:customfield-encryption' has been implemented. This is what triggers the execution of the program when needed.

• Function of the 'Handle' Method
  The new file includes a 'handle' method that executes the action of the console command. This action checks if a custom field (specified by 'db_column_name') is present.

  • If this field exists but isn't encrypted, the method will ensure that the data present within this field in the assets table is encrypted.
  • If the field is already encrypted, an error message will be shown, indicating that the action is unnecessary.
  • If there is no matching field to look for, an error message will indicate that no suitable field was found.

This enhancement is under the App\Console\Commands namespace.

[uberbrady]

This looks great! Nice and clean and straightforward.