tls: update builtin cert bundle for 0.12

[sam-github]

Checklist

• make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

tls

Description of change

Copied certdata.txt from master, rebuilt header using mk-ca-bundle.pl.

Fix #7962

[sam-github]

/to @nodejs/lts If you want it, here it is.

/cc @bnoordhuis In case I did something wrong, but it seems pretty straighforward.

[mscdex]

Is it even worth merging anything v0.12-related at this point? I doubt there will be another v0.12 release before the end of the this month.

[sam-github]

@mscdex I don't know, but @jasnell and @silverwind indicated they thought so. I'm just trying to close out tls/crypto bugs, if we can just close #7962 as "won't do", that's good, too.

[Fishrock123]

I don't think we ended up ever doing the previously scheduled 0.12 release... So I think there will still be one, maybe next week? It was on @rvagg's plate and I can bug him about it again.

[bnoordhuis]

Sam, did you check what certificates have been added and removed? It looks like the last update was three (!) years ago, the changeset is probably quite extensive; possibly quite disruptive too for a final release.

EDIT: It's, marginally, less bad than I originally thought. The commit date is November 2013 but the certdata.txt is actually from November 2014. Ain't git wonderful?

[sam-github]

No, I just made 0.12 support the same as master.

I think leaving 0.12 alone is probably best. This can be reopened if someone feels strongly.