[ethindp-prism] update to 0.11.4

[ethindp]

• 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, or no changes were necessary.
• Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
• All patch files in the port are applied and succeed.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

[ethindp]

@vicroms I'm not really sure how to handle this particular failure. Unless my test env (an ARM64 AWS instance) and the Azure one differ significantly, the problem is that speech dispatcher is no longer being found by pkgconfig. I can't confirm but I suspect the PKG_CONFIG_PATH environment variable is being forced to whatever vcpkg's is, and ignoring system packages completely.

In theory, we could make a libspeechd package. However, the speech dispatcher build system wasn't designed to have separable components. So, you would need dotconf (which is also not in vcpkg from what I can find) and libsndfile even though they will be completely unused by the actual build process. We could patch them out though, I suppose.

An alternative is that we inject a CMakeLists.txt build system and do that. But Idk if vcpkg accepts those kinds of ports.

What are your thoughts? How should I proceed? I could be way off base and Azure could be failing for some other reason but these are the results I'm getting in my test env (which I tried to ensure mirrored Azure as closely as I could manage).

[ethindp]

Update: dotconf looks like it's literally just libc plus posix, so trivially addable. I'll see about submitting a port and that should unblock us with libspeechd, and once libspeechd is in that should unblock us here.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[BillyONeal]

Please fix the conflicts before marking "Ready for review" :)

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[BillyONeal]

The port bits look fine but the version database must only add one new entry.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[BillyONeal]

Thanks!