Don't use new Jackson APIs to avoid classpath issues when parsing AWS configuration

We upgraded the Aws module to avoid deprecation Jackson messages in BEAM-8391 however is pretty common that our users have older versions of Jackson in their clusters. If this happens their code will break because it won't find the new methods that Beam's Aws module is targeting.

AWS SDKv1 for Java dependencies leak an older version of Jackson so this is pretty common for users on EMR who have the AWS dependencies pre provided in the cluster.

Reverting this change makes sense and we should only upgrade these APIs when we decide to move to Jackson 3.x