Is your feature request related to a problem? Please describe.
I added a folder containing a website to IPFS via IPFS Desktop UI and it only presents me with the CIDv0 hash, not the CIDv1 hash. Since subdomain hosting is strongly recommended for any website, I now need to go convert this to CIDv1 before I can use it. When I copy CID via the UI, it just gives me CIDv0.

Describe the solution you'd like
Make it so when I add a file/folder from disk it associates it with a CIDV1 hash by default.

Describe alternatives you've considered

• CIDv1 used everywhere (even when I provide a CIDv0 hash). Maybe there is a good reason for using CIDv0 hashes still?
• Present both CIDv0 and CIDv1 hashes in the UI and let the user copy either. I feel like this is overly complicated?

Additional context
Short term solution may be to just add something in the UI to convert. As it is I spend 5 minutes searching the internet for an online converter tool, fail repeatedly, eventually find some instructions on StackOverflow describing how to convert from CIDv1 to CIDv0, then spin up a docker container for Kubo and run the command. This is, of course, a ridiculous workflow.