Since the new GPO does not exist in the live environment, and if you are using an SQL Database as your configuration store, then you may try
Option # 2 under
Resolution section from the KB article below to delete that GPO from the GPOADmin database.
https://support.quest.com/kb/4374973/unable-to-delete-objects-from-the-lost-and-found-containerOnce you delete the GPO from the database, go back to GPOADmin and refresh the container under version control root where the GPO was created. The GPO should no longer exist in the console.
NOTE: The information in the script(s) provided is known to work successfully; however, they have not been officially tested by Quest Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by Quest Software Support and Development. Quest Support and Development recommends always to make a backup of the current database prior to execution of any script(s) that may modify it.