Build: Synchronize .gitignore and svn:ignore

[dmsnell]

The Core git repo and svn repo have mismatched methods for excluding files, which increases the burden of developing in the git repo and in generating the proper commits for the “build repo.”

At the heart of this is the distinction between how git’s .gitignore contains patterns which apply recursively down the directory hierarchy, but svn’s svn:ignore property applies only to the directory on which it’s set.

In [62155], part of the .gitignore was ported into a svn:global-ignores property, but only as much as was required to fix some broken pieces of the 7.0 release process.

This ticket proposes three actions:

• Audit all of the existing ignores in both repos to discover all discrepancies.
• Move all subversion ignores out of per-directory properties and into a single global property.
• Provide a new script or automation to raise issues when the ignore sets diverge.

Related

• This first appeared during the work on #64393.
• A svn:global-ignores property was introduced in [62155]

[jonsurrell]

I started to look at this and noticed the following differences, assuming .gitignore is more up to date:

Index: tests/phpunit/data
===================================================================
--- tests/phpunit/data  (revision 62164)
+++ tests/phpunit/data  (working copy)

Property changes on: tests/phpunit/data
___________________________________________________________________
Modified: svn:ignore
## -1 +1 ##
-.trac-ticket-cache.*
+.trac-ticket-cache*
Index: .
===================================================================
--- .   (revision 62164)
+++ .   (working copy)

Property changes on: .
___________________________________________________________________
Modified: svn:ignore
## -16,8 +16,9 ##
 vendor
 packagehash.txt
 artifacts
+*.tsbuildinfo
 # Files for local environment config
-/docker-compose.override.yml
+docker-compose.override.yml
 .env
 coverage