Upgrade to most recent timm

[CarlosGomes98]

Is your feature request related to a problem? Please describe.
We are currently stuck at an older version of timm. This is a dependency we inherit from torchgeo, which in turn inherits it from smp. SMP is supposedly working towards using a newer version of timm.
Describe the solution you'd like
We don't really have any tight dependency on smp (we now have a way to support their decoders, but could potentially rework this). We should consider upgrading timm.

This enables some new features, for example, easier ways to directly get intermediate features from backbones, which should make onboarding new backbones much easier.

It might take some refactoring of the models we have registered with timm, but it is probably worth it in the long run

[Joao-L-S-Almeida]

Two questions:

• timm is not explicitly required in requirements/, is that indirectly installed by torchgeo or other ?
• From the most recent tests, I saw that Actions has installed version 0.9.2, should we move to 1.0.* ?

[CarlosGomes98]

• It should be pulled in by torchgeo, but we may want to make that explicit and pull it ourselves
• Im not sure what you mean here :/

[Joao-L-S-Almeida]

@CarlosGomes98 I asked about explicitly updating timm to versions as 1.0.8 or 1.0.9.