Update copyright dates

[chrisklus]

Files that have been modified since the beginning of 2019 should have their copyright year updated, if not already done.

I discussed this with @samreid, and he said that perennial/bin/for-each.sh active-runnables "grunt update-copyright-dates" or perennial/bin/for-each.sh active-runnables grunt update-copyright-dates should handle this in one go.

Relevant slack conversation for how I should proceed regarding {{REPO}}-config.js copyright year:

Sam Reid [1:23 PM]
Oh, also, I have a faint memory that one time this script created a syntax error or lint error (didn’t know how to handle a special case or something). So please check lint-everything after changes.
Also, the *-config.js files are now auto-generated and should not be updated by this tool. Last year around this time was a problem--not sure if resolved. If you see anything related to that, take a closer look or reach out to me.
Good luck!

Chris Klusendorf [1:27 PM]
ooh yeah that’s interesting. i was just testing that, and found that running grunt generate-config will not change a date from “2018” to “2018-2019", but instead will just overwrite to “2019”
should I uncheck all of the -config files in the commit dialog and then revert them?

Sam Reid [1:32 PM]
if you run grunt update-copyright-dates without running generate-config, does it change them?

Chris Klusendorf [1:32 PM]
checking…

Sam Reid [1:33 PM]
It seems safe to run grunt update-copyright-dates then run grunt generate-config afterwards.

Chris Klusendorf [1:33 PM]
yeah i’m seeing it as ignoring config

Sam Reid [1:33 PM]
OK that’s even better
Just do grunt update-copyright-dates by itself then
Taking off for a break, good luck!

Chris Klusendorf [1:34 PM]
okay sounds good, so don’t worry about grunt generate-config at all?
thanks!