Parquet Travis CI jobs to be turned off February 15th

Greetings Parquet PMC,

Infrastructure has reached out to you regarding the Travis CI Open Source policy changes, and the resulting need for Apache projects to migrate away from using Travis.

So far, we have received no response from your PMC.

On February 15th, we will begin the final phase of this migration, turning off Travis builds in order to bring our Travis usage down to 0.

We have found the following repositories mention or make use of .travis.yml files:

- parquet-mr.git
- parquet-cpp.git


You must immediately move to migrate your builds from Travis. If you do not, you will soon be unable to do builds that now rely on Travis.

Many projects have moved to using GitHub Actions, and migrating to GHA is quite straightforward. Other projects use Jenkins providing ARM support, with nodes using the arm label

If you are unsure how to proceed, I would be happy to explain your next steps.

Please at least respond to acknowledge the need to migrate away from Travis, and to tell us your current plans.

Thank you!

**Reporter**: [Xinli Shang](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=shangx@uber.com) / @shangxinli

_{**Note**: *This issue was originally created as [PARQUET-2233](https://issues.apache.org/jira/browse/PARQUET-2233). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Comienza con la documentación de migración referenciada como PARQUET-2502 e inspecciona los archivos .travis.yml de parquet-mr.git y parquet-cpp.git. Determina el plan de migración del proyecto y sustituye las compilaciones basadas en Travis por la CI compatible elegida; se considera terminado cuando Travis ya no sea necesario y la migración esté reconocida.

Escrito por el modelo de indexación a partir del texto del issue.