Locked restore by default

[Fernthedev]

qpm-rust restore default to using a qpm.shared.json as a lock file (or create one if non-existent) and having a qpm-rust update for updating those version ranges in the lockfile?

This PR does a few things:

• Defaults to lock restore if qpm.shared.json exists
• If qpm.shared.json does not exist, defaults to the previous behaviour
• Updates qpm.shared.json::config with qpm.json's fields consistently
• Warns if not using the lock restore mechanism in CI
• Adds some constants for the file names (however, these are unlikely to be unfrozen in the foreseeable future)
• qpm-rust restore --update to revert to the previous restore mechanism

Some of the benefits of this new approach are:

• allows usage for * for dependencies but consistently getting the same dependencies
• CI will always resolve the same deps consistently
• Much faster restore times (skips version range resolving)
• This is how other PM works such as cargo, npm, yarn, etc.

However, this is considered a soft-breaking change as it changes what is widely understood as accepted behaviour in the QPM community. Therefore, great care should be taken into consideration of the side effects of merging this PR.

[sc2ad]

The breaking changes here are very soft, ultimately the restore behavior exists to grab a version of a package that allows for a compile. Ensuring the same range is always set, and doing so by committing the qpm.shares.json file is an improvement towards consistency and reliability of CI runs. This also ensures others who pull will checkout the exact same packages.

Leaving the fallback in is a good idea, but I don't see this being too breaking outside of most people needing to update CI, their gitignore, and making sure they use --update for qpm updates.

[Fernthedev]

I've taken this chance to include another breaking change(s) into consideration:

• Stop generating ./src;./include;./shared folders
• Stop generating qpm.cmake and extern.cmake unless qpm.json::info::additionalInfo::cmake = true

All changes have been tested and successfully working as intended.

[sc2ad]

Default cmake on, how does the restoration work if those folders are not specified? If you remove the folders from being generated, ensure you can publish without all of them + can restore packages without all of them