Extension fails to load with unexpected package.xml

[ghost]

The extension fails when the existing package.xml is in an unexpected (but valid XML) format. Steps to reproduce:

1. Create a package.xml as follows:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
   </types>
   <version>50.0</version>
</Package>

2. Load the extension.

The console output is attached. ExtensionError.log

I would expect that the existing package should be ignored if its not formatted as expected. At minimum the user should be prompted that the existing package.xml is invalid and the plugin should not fail to load.