[restinio] Update to 0.7.1

[eao197]

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• [ ] The "supports" clause reflects platforms that may be fixed by this new version
• [ ] Any fixed CI baseline entries are removed from that file.
• [ ] Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[rcane]

I don't think that the option to use either standalone asio or boost.asio can be a port feature. Those two options are mutually exclusive. And a port feature should only add functionality to a port and not be used to implement alternatives.
So this option can only be overridden in a custom triplet file. I do this myself to use boost.asio with restinio in my triplet file like this

if(PORT MATCHES "restinio")
    set(VCPKG_CMAKE_CONFIGURE_OPTIONS
            -DRESTINIO_ASIO_SOURCE=boost
            -DRESTINIO_DEP_BOOST_ASIO=find
    )
endif()

[BillyONeal]

I agree with @rcane : https://learn.microsoft.com/en-us/vcpkg/contributing/maintainer-guide#do-not-use-features-to-implement-alternatives

[eao197]

@rcane @BillyONeal

So it means that if someone wants to add RESTinio with Boost.Asio to his/her project's manifest file he/she need to write a custom triplet file instead of simple:

{
    "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
    "name": "versions-test",
    "version": "1.0.0",
    "builtin-baseline": "64ca152891d6ab135c6c27881e7eb0ac2fa15bba",
    "dependencies": [
        {
            "name": "restinio",
            "features" : [ "boost-asio" ]
        },
        "json-dto",
        "sqlitecpp"
    ]
}

?

If so, then I think that it simply kills the advantages of vcpkg manifest files :(

Please take into account that some users do not know anything about CMake or/and vcpkg internals and just use vcpkg with VS .sln files without dealing with CMake.

What approach can be used instead of custom triplets? Maybe another port like "restinio-boost" that just binds RESTinio to Boost.Asio? So a user can specify "restinio" or "restinio-boost" in his/her vcpkg.json file.

[eao197]

I've return the port to the old style, without features.

[MonicaLiu0311]

If you're ready, please revert to "Ready for review".