Improve on POST TAP file endpoint and Parser

1. `postTapFiles.js` currently has a hardcoded zip path but needs to be changed to consume a user inputted url to a zip file
2. `Tap.js` currently inserts documents with a hardcoded `url` field and needs to be changed to insert with user inputted url
3. `Tap.js` currently inserts documents with an empty `startBy` field and needs to potentially parse from url the vendor
4. Tap.js` currently inserts documents with an empty `javaVersion` field

Start by reading postTapFiles.js and Tap.js, then trace the POST TAP file endpoint to understand how the zip URL is received. Check how Tap.js currently populates url, startBy, and javaVersion. Done means the endpoint accepts the user-provided zip URL and parsed or supplied metadata is stored instead of the current hardcoded or empty values.

Written by the indexing model from the issue text.