Refactor dotorg deploy script to use an EXCLUSION list instead of INC…

[pbking]

This script runs on every commit of trunk. It attempts to push any version of themes that are NEWER in the github repo than are present in wporg.

Because this currently uses an INCLUSION list only the themes in that list are automatically updated on dotorg. This has resulted in a lot of themes falling behind and necessitates a manual submission process.

This refactors the dotorg deploy script to

• use an EXCLUSION list instead of INCLUSION list
• ignore ALL classic themes
• check existence of themes and version using HTTP instead of SVN

The result of this change would (immediately) push the following themes:

➤ Upgrading archivo/ from 1.0.4 to 1.0.6 ➤ Upgrading bibliophile/ from 1.0.3 to 1.0.4 ➤ Upgrading bsoj/ from 1.0.2 to 1.0.3 ➤ Upgrading common/ from 1.0.4 to 1.0.5 ➤ Upgrading freddie/ from 1.0.1 to 1.0.2 ➤ Upgrading jinjang/ from 1.0.0 to 1.0.1 ➤ Upgrading kigen/ from 1.0.2 to 1.0.3 ➤ Upgrading loudness/ from 1.0.5 to 1.0.10 ➤ Upgrading optimismo/ from 1.0.2 to 1.0.3 ➤ Upgrading tomoni/ from 1.0.2 to 1.0.3 ➤ Upgrading trellick/ from 1.0.2 to 1.0.4

[vcanales]

I've refactored the script to read ignore paths from a .dotorg-ignore file. I also refactored rsync commands that were using a separate dotorg-excludes.txt file, to use the same file as the theme deployment.

I think it makes sense to keep the list consolidated, with both general paths and theme paths that we don't want to include in our dotorg deployments.