Update the "New Bug" page on Core Trac

[mikesherov]

The "new bug" page on the core bug tracker needs several improvements:

• the giant red banner at the top has links to the deprecated docs site, those need to be updated or removed.
• the giant red banner has too much text and too many options. Needs to be dramatically simplified.
• It should warn, but not prevent submission, when an external link like jsbin or jsfiddle is not present
• it should require an email address for the submission, but provide an option to make that email address private, and only used for communication
• it should do a rudimentary duplicate search before submission, similar to what stackoverflow.com does when attempting to submit a question

[ajpiano]

Would be amazing to also see if we could identify the characteristics of "bugs" that are actually support tickets, and create a mechanism to automatically close those accordingly, directing the reporter to the appropriate support resources without requiring intervention from the triage team. Though maybe this goes beyond the scope of the "new bug" page itself.

[dmethvin]

I'd like to prevent people from filing bugs that aren't bugs. A little bit of jQuery on the form could help there. For example, we have a field for a link to a test case, and require them either to fill it in with a link or say "no test case needed." Also I'm not sure we need the version field, it should either be for the current version or -git and older versions don't matter unless they're reporting a regression with the current one.