Failed to Populate DD Tables After Upgrade From 5.7 to 8.0

[Jacob Gatten]

As the title states, I am running into an error after attempting to upgrade a 5.7.36 DB to 8.0.33. Here are the full startup logs:

2023-12-11T21:01:26.777200Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2023-12-11T21:01:26.777296Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2023-12-11T21:01:26.779893Z 0 [Warning] [MY-010101] [Server] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2023-12-11T21:01:26.780024Z 0 [System] [MY-010116] [Server] /usr/local/mysql/bin/mysqld (mysqld 8.0.33) starting as process 1392452
2023-12-11T21:01:26.811978Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=1073741824. Please use innodb_redo_log_capacity instead.
2023-12-11T21:01:26.814294Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2023-12-11T21:01:26.814336Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-12-11T21:01:27.450427Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-12-11T21:01:43.283493Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2023-12-11T21:01:43.283561Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-12-11T21:01:45.762435Z 0 [System] [MY-010910] [Server] /usr/local/mysql/bin/mysqld: Shutdown complete (mysqld 8.0.33) MySQL Community Server - GPL.

I have previously seen this error upgrading other 5.7 DBs but this one is unique. Typically, I would see another error in the logs prior to the "Failed to Populate DD tables" error and upon fixing those issues the DD error would go away. For some reason in this instance though, MySQL does not give me any indication as to what the root cause actually is. I have made sure to run the checkForServerUpgrade utility in MySQL Shell version 8.0.35 and also received back zero errors. I am at a loss where to go next; any help is greatly appreciated!