6634 primefaces8

[scolapasta]

What this PR does / why we need it:
Upgrades Primefaces to the latest v8.

Which issue(s) this PR closes:

Closes #6634
Closes #6557

Special notes for your reviewer:
changes were surgical and are due to changes in primefaces APIs or moving some popup code

Suggestions on how to test this:
Smoke / regression tests; no new functionality. (though upload component now allows files without extension, so that should be tested in order to close #6557)

Does this PR introduce a user interface change?:
no (except in allowing users to upload files without extensions)

Is there a release notes update needed for this change?:
Might be worth mentioning the upgrade, but nothing special needs to be done.

Additional documentation:

[coveralls]

Coverage remained the same at 19.661% when pulling e9e186b on 6634-primefaces8 into e5413e2 on develop.

[sekmiller]

Looks good. There were a couple of stray duplicate imports of the PF uploadedFile, but I took them out.

[kcondon]

Issues found so far:
x1. Uploading 3 files to s3 direct causes file upload to not complete, no errors, progress bars stuck.
Update: This appears to be an intermittent/timing? issue with direct to s3 on dataset create. Will do further testing and open a new ticket. Happens on develop too.
x2. Host Dataverse type ahead/lookup logic not working after lookup failure/correction on create dataset page. Does not try again. Update: This is now also broken on develop branch, was working recently.
3. On dataset create, flurry of server log entries (6) of this type:
this also happens when click log on.

[2020-04-16T15:15:15.184-0400] [glassfish 4.1] [WARNING] [jsf.externalcontext.no.mime.type.found] [javax.enterprise.resource.webcontainer.jsf.context] [tid: _ThreadID=150 _ThreadName=jk-connector(3)] [timeMillis: 1587064515184] [levelValue: 900] [[
  JSF1091: No mime type could be found for file bs/css/bootstrap.min.css.map.  To resolve this, add a mime-type mapping to the applications web.xml.]]

[scolapasta]

For #2, since it also seems to happen on dev, doesn't seem to be PF8 related, specifically. Regardless, we've decided to remove this component completely for a better designed solution (#6772). So I don't think it's worth the effort to fix as it will be gone soon - that issue is in the Up Next column and should be complete before the next release.

I'll copy over the report to that issue, just so we can track, it there if need be.

[kcondon]

@scolapasta I'm going to merge this since all functional stuff is working but there is that one extra logging issue, which I'll open as a separate ticket.