Resolve bandstructure datastore bug

[JaGeo]

Closes #584.

I added "bandstructure" to the list of object names that should be saved in the datastore. I think it is related to how emmet saves the bandstructures:
https://github.com/materialsproject/emmet/blob/08f143833ac6ba5732abadb7beee9e424d0220cf/emmet-core/emmet/core/vasp/calculation.py#L49

For DOS, I assume it works by accident.

[JaGeo]

It would be great if someone of the maintainers tests this as well as I cannot really write a test for this. If I can test it, please let me know how. Thanks.

@Zhuoying @janosh @utf?

[codecov]

Codecov Report

Merging #605 (207c52a) into main (e6a58e9) will decrease coverage by 0.17%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #605      +/-   ##
==========================================
- Coverage   75.67%   75.51%   -0.17%     
==========================================
  Files          83       83              
  Lines        6792     6792              
  Branches     1002     1002              
==========================================
- Hits         5140     5129      -11     
- Misses       1340     1352      +12     
+ Partials      312      311       -1     

Files	Coverage Δ
src/atomate2/vasp/jobs/base.py	96.49% <ø> (ø)

... and 1 file with indirect coverage changes

[JaGeo]

Maybe, we also need to change all names there or directly import the data objects from emmet

[utf]

Thanks very much @JaGeo. I just added a note with a reminder to fix BandStructure MSONable later.

[JaGeo]

@utf Thanks for responding and resolving it so quickly.