Refactor logging configuration and setup

[mitchellhenke]

🎫 Ticket

Link to the relevant ticket: https://gitlab.login.gov/lg-people/platform/radia/radialegacy-09.15.23/-/issues/100

🛠 Summary of changes

As part of moving towards doing log rotation, We will be exploring adding additional configuration when instantiating Loggers. This PR makes a few changes to minimize instantiations and have a single point of access for a given file's logger and hopefully help avoid differing configurations going forward.

This includes:

• Having the IdentityJobLogSubscriber use the ActiveJob logger which has the side benefit of making the class more thread-safe by eliminating the class instance variable
• Moving the KMS logger into application configuration rather than as a class instance variable and similar benefit as above with thread-safety
• Moving the events logger into application configuration rather than creating a new instance every time (this may also have minor performance benefits)
• Eliminating the visit logging which doesn't appear to be used or referenced anywhere (presumably due to server_side_visits being set to false)
• Using Rails logger for the AWS logger which fixes a bug where the AWS logger would not respect the STDOUT logging configuration
• Moving all of the log filenames into the constants file so that they are available prior to application boot
• Removing the reports_logger (which was removed in Stop writing data to reports.log (LG-9415) #8143)

I will be testing this in my sandbox prior to merging, but wanted to open this for review.