Introduce a new Feature enum to improve the Features facade

[caendesilva]

Abstract

Cherry picks some changes from #1647 and #1649 in order to make the v2 upgrade path smoother. See https://twitter.com/CodeWithCaen/status/1777647925939593341

Using Enums for this improves the type safety and IDE support. For example if you use Hyde::hasFeature() which now takes an enum instead of a string, your IDE will provide autocomplete and warn if you use a feature that is not supported by Hyde. Due to these simplifications the old static feature flag methods have been removed. To upgrade, replace the following method usages (where the array key is the old syntax and the value is the new)

use Hyde\Facades\Features;
use Hyde\Enums\Feature;

[
    Features::htmlPages()           => Feature::HtmlPages,
    Features::markdownPosts()       => Feature::MarkdownPosts,
    Features::bladePages()          => Feature::BladePages,
    Features::markdownPages()       => Feature::MarkdownPages,
    Features::documentationPages()  => Feature::DocumentationPages,
    Features::darkmode()            => Feature::Darkmode,
    Features::documentationSearch() => Feature::DocumentationSearch,
    Features::torchlight()          => Feature::Torchlight,
]

Upgrade Path

To upgrade to use the enum cases instead of the now deprecated static features methods, simply replace the following usages:

PhpStorm Automatic Refactors

If you are using PhpStorm, you can follow these steps to do it automatically

Step 1: Put your caret on one of the deprecated method calls in the features array in the config/hyde.php file

Step 2: Run Alt+Enter to open the context menu

Step 3: On the highlighted option, press right arrow to open the submenu and "Fix all deprecated problems in file"

Step 4: Move the cursor to the added Feature class and open the context menu again

Step 5: Select the "Import class" option

Step 6: Done!