Summary

This Pull Request makes possible to enable or disable the Tenor GIF picker availability accordingly to the selected WordPress build type. This change adds to the issue 11456.

Wasabi and Zalpha	Vanilla

The solution proposes the following implementation:

• The BuildConfig now receive the declaration of the boolean TENOR_AVAILABLE field directly from the build.gradle.

• The button availability to select the Tenor GIF picker follows the TENOR_AVAILABLE value, if the value is false, the button doesn't get configured and should never appear on the screen.

• The TENOR_AVAILABLE is set as true for the Wasabi and Zalpha builds and false for the Vanilla build.

Testing from the Post Editor

with Wasabi and Zalpha build

1. Click to create a new post
2. Click on the overflow button at the top right end of the screen
3. select the Switch to classic editor
4. Click on the plus (+) button at the bottom left end of the screen
5. Verify that the Choose from Tenor option is available
6. Type in the search bar to query GIFs
7. Once inside the Gif Picker, make sure that selection, preview and add are all working as expected

with Vanilla build

1. Click to create a new post
2. Click on the overflow button at the top right end of the screen
3. select the Switch to classic editor
4. Click on the plus (+) button at the bottom left end of the screen
5. Verify that the Choose from Tenor option isn't there

Testing from the Media Browser

with Wasabi and Zalpha build

1. Go to the Media Browser
2. Click on the Add button at the top right
3. Verify that the Choose from Tenor option is available
4. Type in the search bar to query GIFs
5. Once inside the Gif Picker, make sure that selection, preview and add are all working as expected

with Vanilla build

1. Go to the Media Browser
2. Click on the Add button at the top right.
3. Verify that the Choose from Tenor option isn't there

PR submission checklist

• I have considered adding unit tests where possible.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.