Add ability to filter locations of proguard mapping file

Description of the feature request

We use a third party plugin that creates it’s own proguard mapping.txt file. This file is stored in a different location from the other proguard mapping.txt file. This caused an issue when using the android-build step. The android build step looks for all files with the name mapping.txt and ignores the directory they are in. It then renames the file and appends a timestamp for duplicated files. These files are then moved to the deploy dir.

This caused an error when trying to upload to the google play store because the mapping file used to upload was the incorrect one.

Use case / for what or how I would use it

I would like the ability to filter or ignore mapping files outside of the build/outputs/mapping/[build type] folder. Something similar to the app artifact location pattern in the android build would also work.