Add data files for new illuminants.

[mkcor]

Description

Following up with #5234 -- only adding the new data here.

Checklist

• Docstrings for all functions
• Gallery example in ./doc/examples (new features only)
• Benchmark in ./benchmarks, if your changes aren't covered by an
  existing benchmark
• Unit tests
• Clean style in the spirit of PEP8

For reviewers

• Check that the PR title is short, concise, and will make sense 1 year
  later.
• Check that new functions are imported in corresponding __init__.py.
• Check that new features, API changes, and deprecations are mentioned in
  doc/release/release_dev.rst.

[pep8speaks]

Hello @mkcor! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file skimage/data/_registry.py:

Line 44:80: E501 line too long (110 > 79 characters)
Line 46:80: E501 line too long (109 > 79 characters)
Line 47:80: E501 line too long (110 > 79 characters)
Line 48:80: E501 line too long (109 > 79 characters)
Line 49:80: E501 line too long (109 > 79 characters)
Line 50:80: E501 line too long (110 > 79 characters)
Line 51:80: E501 line too long (109 > 79 characters)
Line 52:80: E501 line too long (109 > 79 characters)
Line 55:80: E501 line too long (111 > 79 characters)
Line 58:80: E501 line too long (111 > 79 characters)
Line 61:80: E501 line too long (111 > 79 characters)
Line 64:80: E501 line too long (111 > 79 characters)
Line 66:80: E501 line too long (110 > 79 characters)
Line 67:80: E501 line too long (109 > 79 characters)
Line 68:80: E501 line too long (110 > 79 characters)
Line 70:80: E501 line too long (109 > 79 characters)
Line 71:80: E501 line too long (110 > 79 characters)
Line 72:80: E501 line too long (109 > 79 characters)
Line 73:80: E501 line too long (109 > 79 characters)
Line 74:80: E501 line too long (110 > 79 characters)
Line 75:80: E501 line too long (109 > 79 characters)
Line 76:80: E501 line too long (109 > 79 characters)
Line 79:80: E501 line too long (111 > 79 characters)
Line 82:80: E501 line too long (111 > 79 characters)
Line 85:80: E501 line too long (111 > 79 characters)

[mkcor]

The current test fail is not specific to this PR.

@hmaarrfk @BierretA I have manually cherry-picked the new (non-duplicate) data files from #5234.

[mkcor]

@hmaarrfk please review/approve ;)

[hmaarrfk]

It seems that adding the files to the registry itself causes test to fail.

I noticed that the azure pipelines all build off the build wheels.

They will fail without a pull request like this.

[hmaarrfk]

I'm kinda ok with this, but I think that merging #5283 would have caused fewer failures.

I can't really inspect the azure failures, but in either case, it is clear that the build system has stopped that PR from going through.

I would be ok just merging the main PR as is.

[mkcor]

It seems that adding the files to the registry itself causes test to fail.

Yes, because the files don't live in main yet! So, if we merge this PR first, then we can go on with the data registry update (via a PR which will pass CI).

[mkcor]

I'm kinda ok with this, but I think that merging #5283 would have caused fewer failures.

@hmaarrfk "would cause" 😉 Let's fix the CI script first, of course!

[mkcor]

Let's move forward with this, now that #5283 is merged! /cc @grlee77 @jni