[makeid] Add new port

[Pospelove]

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[dg0yt]

There can't be different versions (and SHA512) with the same name.
Can we use FILENNAME "MakeID.h-${VERSION}" here (and in the copy command below)?

[BillyONeal]

I'm a bit concerned over 'makeid' since that seems likely to be a conflicting name but I can't find any actual conflicts so I guess this works.

If you know how to contract upstream it would be good to ask them to make versioned download locations.

[dg0yt]

I'm a bit concerned over 'makeid' since that seems likely to be a conflicting name.

In that case we should quickly move it to a subdir...

[BillyONeal]

I'm a bit concerned over 'makeid' since that seems likely to be a conflicting name.

In that case we should quickly move it to a subdir...

I didn't find any actual conflicts so I don't think it needs a subdir. Unless we see actual conflicts.