win32: Add version resource and manifest

[k-takata]

This adds version resource and application manifest to the win32 executable file.
win32/ctags.rc and win32/resource.h are created by VS2013 and edited manually.

The application manifest should fix the issue #1837 on Windows 10 version 1903 or later.
See: https://docs.microsoft.com/en-us/windows/uwp/design/globalizing/use-utf8-code-page
This is a relatively new feature in Windows and it might not be matured enough, but at least I confirmed that ctags.exe can handle Unicode file names on Windows 10 1909.

NOTE: the version number needs to be updated manually.
We have version numbers in several files: configure.ac, docs/conf.py, main/ctags.h, win32/ctags.exe.manifest and win32/ctags.rc. (The last two files are added in this PR.)
We need to update all of them, when we release a new version.

[coveralls]

Coverage remained the same at 86.372% when pulling 105f514 on k-takata:win32-add-resource into 2ebf5b1 on universal-ctags:master.

[codecov-io]

Codecov Report

Merging #2360 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2360   +/-   ##
=======================================
  Coverage   86.25%   86.25%           
=======================================
  Files         176      176           
  Lines       35717    35717           
=======================================
  Hits        30808    30808           
  Misses       4909     4909

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ebf5b1...105f514. Read the comment docs.

[masatake]

I don't have enough knowledges to review this. Feel free to merge this when you think you are o.k.

[k-takata]

Do you have any comments about the commit messages, or about usage of autotools and makefiles?

[masatake]

I have only one very minor suggestion.

[masatake]

NOTE: the version number needs to be updated manually.
We have version numbers in several files: configure.ac, docs/conf.py, main/ctags.h, win32/ctags.exe.manifest and win32/ctags.rc. (The last two files are added in this PR.)
We need to update all of them, when we release a new version.

I see. Instead of improving our build-sys for synchronizing them, verifying the consistency of them at on travis may be easy. I like the technique you introduced for converting man to docs/man. Implementing verifier is much easier, but effective.

[k-takata]

Instead of improving our build-sys for synchronizing them, verifying the consistency of them at on travis may be easy.

We need to verify the following points:

ctags/configure.ac

Line 10 in 105f514

AC_INIT([universal-ctags],[0.0.0])

ctags/docs/conf.py

Lines 55 to 58 in 105f514

	# The short X.Y version.
	version = '0.3.0'
	# The full version, including alpha/beta/rc tags.
	release = '0.3.0'

ctags/main/ctags.h

Line 20 in 105f514

# define PROGRAM_VERSION "0.0.0"

ctags/win32/ctags.exe.manifest

Line 3 in 105f514

<assemblyIdentity type="win32" name="Universal Ctags" version="0.0.0.0" />

ctags/win32/ctags.rc

Lines 61 to 62 in 105f514

	FILEVERSION 0,0,0,0
	PRODUCTVERSION 0,0,0,0

ctags/win32/ctags.rc

Line 79 in 105f514

VALUE "FileVersion", "0.0.0.0"

ctags/win32/ctags.rc

Line 84 in 105f514

VALUE "ProductVersion", "0.0.0.0"

Note that Windows uses X.Y.Z.W (or X,Y,Z,W) style, not X.Y.Z. Maybe we should set to X.Y.Z.0.