SSL4EO-L Weights

[nilsleh]

This PR adds the SSL4EO-L Weights as Enums

[nilsleh]

@adamjstewart I just added a couple to see if the formatting and naming etc is okay, before adding the rest.

[adamjstewart]

I'm thinking we should have a single repo on HF for all Landsat weights. What do you think?

[adamjstewart]

Trying to decide if we should rename our model repo to ssl4eo_l or our dataset repo to ssl4eo_landsat. What do you think?

[nilsleh]

I feel like ssl4eo_landsat is a lot more clear and worth the extra characters, I didn't think about it when creating the HF repo, just thought it would be the clearest description

[adamjstewart]

Alright, let's go with that then. Naming looks good here so you can upload the rest of the weights. I'm not exactly sure how the U-Net weights work, but we want those too.

We can submit a separate PR to rename the HF repos for the datasets. For the existing weights, I would like to organize them like we do here, but the difference is that we can't delete the old names (at least for some time) since older releases depend on those names.

[adamjstewart]

Do we not have any U-Net pre-trained weights we can upload? We at least have the cloud cover models on our cluster. Not sure if the framework is in place to load those weights though...

[adamjstewart]

None of the weights are in the right format...

missing_keys = ['cls_token', 'pos_embed', 'patch_embed.proj.weight', 'patch_embed.proj.bias', 'blocks.0.norm1.weight', 'blocks.0.norm1.bias', ...]
unexpected_keys = ['state_dict', 'hyper_parameters']