Resolve Horizon CI failures caused by the failure to install the right version of libc++

[urvisavla]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've updated the relevant CHANGELOG (here for Horizon) if
  needed with deprecations, added features, breaking changes, and DB schema changes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

What

Update this fix to handle all versions of libc++

Why

Horizon CI is failing with errors while running integration test. The error occurs because the apt package manager is unable to install the required version of libc++ (libc++1-12) when there is already an existing version installed.

2023-07-27T17:08:37.2546428Z Reading package lists...
2023-07-27T17:08:37.4156798Z Building dependency tree...
2023-07-27T17:08:37.4169264Z Reading state information...
2023-07-27T17:08:37.4714457Z Some packages could not be installed. This may mean that you have
2023-07-27T17:08:37.4715476Z requested an impossible situation or if you are using the unstable
2023-07-27T17:08:37.4716439Z distribution that some required packages have not yet been created
2023-07-27T17:08:37.4716842Z or been moved out of Incoming.
2023-07-27T17:08:37.4717193Z The following information may help to resolve the situation:
2023-07-27T17:08:37.4717408Z 
2023-07-27T17:08:37.4717574Z The following packages have unmet dependencies:
2023-07-27T17:08:37.5522389Z  libc++1-12 : Conflicts: libc++-x.y
2023-07-27T17:08:37.5523382Z  libc++1-14 : Conflicts: libc++-x.y
2023-07-27T17:08:37.5526307Z  libc++abi1-12 : Conflicts: libc++abi-x.y
2023-07-27T17:08:37.5529085Z  libc++abi1-14 : Conflicts: libc++abi-x.y
2023-07-27T17:08:37.5531166Z  libunwind-12 : Conflicts: libunwind-x.y
2023-07-27T17:08:37.5531937Z  libunwind-14 : Conflicts: libunwind-x.y
2023-07-27T17:08:37.5559422Z E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
2023-07-27T17:08:37.5590668Z ##[error]Process completed with exit code 100.

Known limitations

[TODO or N/A]

[2opremio]

@urvisavla I would suggest listing what packages are installed:

apt list --installed |  grep libc++

[2opremio]

We may even be able to make this future proof by doing:

sudo apt-get remove -y libc++1-* libc++abi1-*

instead of

sudo apt-get remove -y libc++1-10 libc++abi1-10

[2opremio]

That seems to have solved it, nice!

[urvisavla]

That seems to have solved it, nice!

Yes, thank you!! We are currently running tests on both Ubuntu 20.04 and 22.04. The first one has libc++1-10, while the second one has libc++1-14. This discrepancy in the version explains why updating the version to remove libc++1-14 didn't work. Using libc++1-* was the fix so thank you for the solution.
Also, if it's alright i'd like to keep this line as well sudo apt list --installed | grep libc++ because that really helped.