[many ports] Include functional to fix error C2039 and C2504

[LilyWangLL]

In an internal version of Visual Studio, many ports install failed with following error:

error C2039: 'binary_function': is not a member of 'std'
error C2504: 'binary_function': base class undefined
error C2143: syntax error: missing ',' before '<'

Or

error C2039: 'unary_function': is not a member of 'std'
error C2504: 'unary_function': base class undefined
error C2143: syntax error: missing ',' before '<'

The reason is new STL change, need include <functional> to fix them.

• 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.

I have submitted an issue on upstream:
kpu/kenlm#428
themoos/core-moos#71

[Neumann-A]

error C2039: 'binary_function': is not a member of 'std'
error C2039: 'unary_function': is not a member of 'std'

maybe patch the use of these functions out since they have been deprecated since c++11 and are removed in 17 (Maybe there is an update upstream which already does this?)

[BillyONeal]

maybe patch the use of these functions out since they have been deprecated since c++11 and are removed in 17 (Maybe there is an update upstream which already does this?)

I think that crosses into 'upstream needs to be in the loop' territory where just add standard library header can be considered 'fairly mindless'.

[BillyONeal]

Tagging vcpkg-team-review for the 'rename upstream targets' question.

[BillyONeal]

I think @dg0yt has pointed out a legitimate problem with the edits to libsbml. It might be a good idea to separate that into its own PR since it is very much not "include functional" like the other changes here.

Thanks!

[LilyWangLL]

I think @dg0yt has pointed out a legitimate problem with the edits to libsbml. It might be a good idea to separate that into its own PR since it is very much not "include functional" like the other changes here.

Thanks!

Done. I reverted the changes of libsbml, I will submit a new PR to update libsbml.

[BillyONeal]

Thanks for the fixes!