fix: Android build for compileSdk < 33

[kkafar]

Description

#1693 introduced new animation xml's with features available only since API level 33 (Android 13). This resulted in build failures in cases where compileSdk/targetSdk is set to value lower than 33.

Note: placing these animations in qualified resource directory res/anim-v33 did not resolve the issue, because the qualifier is only used during runtime - in build phase all resources must be valid from the perspective of given SDK (at least it seems so).

I thought of few options:

1. Having separate res directories for compileSdk >= 33 and compileSdk < 33 and selecting appropriate in build.gradle.
   The main disadvantage is that most of the animation resources are being duplicated and any future modifications will require us to remember to modify both versions of resources.

2. Keeping only new animation files in separate directory and copying them into res/anim-v33 during gradle configuration phase only when appropriate.
   This also would require us to modify files in two places, but only few ones, which is slightly better IMO.
   The emphasis on configuration phase comes from the fact, that it will work Android Studio nicely (gradle sync).

As for now I went with option 2.

Changes

Added manageV33Animations task to build.gradle which:

1. Copies v33 xmls inside res/anim-v33 when compileSdk >= 33
2. Deletes res/anim-v33 when compileSdk < 33

Test code and steps to reproduce

Build any Android example with various compileSdk set and observe how resource files change (also check out #1693)

Checklist

• Ensured that CI passes