Remove all elements from allowlists in source_code_test.py

[gabrieldemarmiesse]

We enforce some rules in source_code_test.py about what API we can't use in addons. (no private api, no tf.compat.v1, and no experimental API in user-facing code).

We didn't enforce it in some files because they didn't respect the rules before the check was put into place. Replacing the problematic code takes some time, so this is why there are blacklists now. To track the progress. Replacing some APIs by public ones can be very easy or very hard depending on what the code is about. We'll gladly take pull request removing some elements from the blacklists. When we remove all elements, we can remove the blacklists entirely.

It's possible to copy the code needed into addons, or to find another similar API as long as the effect is the same.

[fsx950223]

#1324
Rollback?

[gabrieldemarmiesse]

@fsx950223 I think we need to copy the code of the wrapper in Addons (we may already have some of it) and use that instead.

[fsx950223]

@fsx950223 I think we need to copy the code of the wrapper in Addons (we may already have some of it) and use that instead.

It's difficult if the wrapper API depends on lots of internal APIs.

[gabrieldemarmiesse]

We can limit the functionality to our use cases if that can help. For example, we don't support tf.compat.v1. The wrapper in TF seems fairly small, I think we should be able to port it.

[seanpmorgan]

TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision:
TensorFlow Addons Wind Down

Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA:
Keras
Keras-CV
Keras-NLP