title: AMO CI always gives Duplicate add-on ID found
body: <p>I'm currently trying to automate updates of my web extension in my build pipeline with this API / endpoint <a href="https://addons.mozilla.org/api/v3/addons" rel="nofollow noreferrer">https://addons.mozilla.org/api/v3/addons</a>.</p>
  
  <p>So the actual command that I'm using looks like this:</p>
  
  <pre><code>curl "https://addons.mozilla.org/api/v3/addons/" -g -XPOST --form "upload=@dist/firefox/psono.firefox.PW.zip" -F "version=1.0.17" -H "Authorization: JWT ABCDEFG..."
  </code></pre>
  
  <p>(documentation here <a href="http://addons-server.readthedocs.io/en/latest/topics/api/signing.html#uploading-without-an-id" rel="nofollow noreferrer">http://addons-server.readthedocs.io/en/latest/topics/api/signing.html#uploading-without-an-id</a> )</p>
  
  <p>I'm now where I always get (after a lot of tries and errors with the authentication):</p>
  
  <pre><code>{"error":"Duplicate add-on ID found."} 
  </code></pre>
  
  <p>I have in my manifest this:</p>
  
  <pre><code>"manifest_version": 2,
  "name": "psono.PW",
  "description": "Psono Password Manager",
  "version": "1.0.17",
  
  ... alot of other stuff ...
  
  "applications": {
      "gecko": {
          "id": "{3dce78ca-2a07-4017-9111-998d4f826625}"
      }
  }
  </code></pre>
  
  <p>If I remove this "applications" attribute, then it passes, but it creates a new extension instead of updating the existing one. I already diffed the manifest of my existing extension and my new one, and besides some formatting of the JSON and the obvious difference of the version attribute, they look identical.</p>
  
  <p>What am I missing, that the AMO API cannot actually match my update with my existing extension?</p>