Optimize Deployment to WordPress.org

[kevinfodness]

Description

We should eliminate the develop-built branch workflow and instead build assets as we are deploying to WordPress.org:

1. Remove the .deployignore file in favor of the .distignore file
2. Change the configuration for tagging a release to not use a -built branch and not build assets at all, and instead just tag develop at the proper point in time; this step should also not use the .distignore file, since we need those files to be present
3. Change the configuration for the push to WordPress.org so that it builds the assets before pushing

Use Case

We should be able to push content to WordPress.org on demand, and should be able to have the asset build process only build assets when pushing instead of storing them in the repo in a built branch.