1.0 Release

[sudara]

This is a big bundle o 1.0 joy.

The only thing that didn't make the release this time was packages support for macOS.

Still doing .dmg releases. Which is funny, because drag and dropping plugins from DMG is fixed and working again as of Ventura.

Anyway, this PR bundles the following:

• Improves commenting around all CMake functionality
• Resolves Make Major versioning default #40
• Fixes [small formatting improvement] comments in "juce_add_plugin" section #32
• Fixes Target executable shouldn't be set for the ALL target #34
• Closes Is the Xcode specific config still necessary? #35
• Fixes Refactor some of the hairier cmake stuff into includes #36
• Fixes Add example module #37
• Fixes Standalone support #39
• Fixes Is linking juce modules with PUBLIC visibility dangerous? #31
• Closes Fix key expiration on Azure, update blog article #38
• Exposes PRODUCT_NAME_WITHOUT_VERSION (as JucePlugin_Name doesn't use the nicer PRODUCT_NAME)
• Exposes CMAKE_BUILD_TYPE
• Resolves Separate out Benchmarks target from Tests target #42
• Moves to using lowercase names for root level directories like source and tests (was scaring away the gen z'ers!)

f637d79 attempted to fix #31 by putting the juce modules (and third party modules) back to PRIVATE visibility. See that issue for details on why this needs to be the case in JUCE.

Unfortunately, that fix doesn't account for the fact that differing compile definitions may be desired on each target. For example we might want to set JUCE_MODAL_LOOPS_PERMITTED=1 in tests to be able to run the MessageManager so callbacks fire, or set something like RUN_MY_TESTS=1 so that tests in source files and module directories will run. Trying to add additional definitions via target_compile_definitions wasn't working.

This PR implements @chrhaase's suggestion of sticking all app code and config in an INTERFACE target so that it can be shared between the various juce plugin targets as well as the Tests target.