[C++] SO versioning schema after release 1.0.0

[asfimport]

Described by @kou on the mailing list:

If we may break ABI compatibility each minor version up
release ("Y" is increased in "X.Y.Z"), we should include
minor version into SO major version (100, 101 and 102 in the
following examples):

• 1.0.0 -> libarrow.100.0.0

• 1.1.0 -> libarrow.101.0.0

• 1.2.0 -> libarrow.102.0.0

  If we don't break ABI compatibility each minor version up
  release, we just use the same SO major version (100 in the
  following examples) in 1.0.0:

• 1.0.0 -> libarrow.100.0.0

• 1.1.0 -> libarrow.100.1.0

• 1.2.0 -> libarrow.100.2.0

Reporter: Krisztian Szucs / @kszucs
Assignee: Krisztian Szucs / @kszucs

PRs and other links:

• GitHub Pull Request #4801

_{Note: This issue was originally created as ARROW-5848. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou:
I added a workaround in #4791

[asfimport]

Antoine Pitrou / @pitrou:
Issue resolved by pull request 4801
#4801