fix!: Use SHA-256 for the config file name

[silverwind]

Fixed a maximum line length eslint warning on this line as well. This change doubles the length of the file name from a previous 32 hex characters to 64.

SHA-256 was added in OpenSSL 0.9.8, released 2005-06-06, so every Node.js version should have it.

Fixes #56

[phated]

One thing that we need to be conscious of for this is that the increase in filename length might cause Windows systems to fail with a max filepath limit.

We might want to release this as a breaking change due to that ☝️

[silverwind]

Indeed, thought I do consider it unlikely we'll reach MAX_PATH of 260 chars. In the general case the path will be something like

C:\Users\<username>\AppData\Local\js-v8flags\.v8flags-1-8.1.307.31-node.33.<hash>.json

which is around 135 chars + length of the username, so should be well within that limit.

[tgflet]

Bump, I could really use this fix in a project. It is breaking the project when enforcing FIPS when enforcing FIPS because MD5 is not FIPS compliant @silverwind @phated

[phated]

@Shawn1874 As with all open source, it'll get done when it gets done. It wasn't until recently that gulp started to have any significant sponsors since all funding disappeared since covid.

[phated]

Thanks for this @silverwind! Sorry for the delay, but wanted to include this in the next major in case it breaks someone.