Always use different tags for k3s image updates

[AhmedHanafy725]

With each update for the k3s image, please make sure to have a flist with a new tag to be used in the deployments cause we may run into errors when adding a new worker (has a new k3s version or new configuration) to an old cluster.

Please open an issue for ts-sdk and go-sdk with each new flist to be used.

[hossnys]

• as the latest k3s version released from k3s is 1.31.0 , so we'll update our image to have this version but on base image 24.04 , and push a new image with the new released tag not using latest tag again.

[hossnys]

• changes made at this PR update k3s version to 1.31.0 with 24.04 as base image #299
• new docker image created : threefolddev/k3s:v1.31.0
• new flist also done here : https://hub.grid.tf/samir1.3bot/threefolddev-k3s-v1.31.0.flist

[hossnys]

• flist tested on devnet dashboard :

[hossnys]

• PR approved and merged .
• @maxux could you please promote this flist https://hub.grid.tf/samir1.3bot/threefolddev-k3s-v1.31.0.flist , using the same name please .

[maxux]

Promoted: https://hub.grid.tf/tf-official-apps/threefolddev-k3s-v1.31.0.flist.md

[hossnys]

done