Revert of Move geometry interface files to geometry directory.

Revert of Move geometry interface files to geometry directory. (patchset #7 id:120001 of https://codereview.chromium.org/2741723005/ )

Reason for revert:
Findit identified CL at revision 459398 as the culprit for
failures in the build cycles as shown on:
https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzczZjIyMDg4ZWIyYzk0ZGY0MmVkZDU1YWJkOWNmMWUzNDVlMThlN2MM

Original issue's description:
> Move geometry interface files to geometry directory.
> 
> The geometry interfaces such as DOMMatrix, DOMRect and so on can be shared 
> in a lot of modules such as dom, css and so on. Also, it is not very relevant to
>  the DOM, so it is proper to create a new geometry directory and then move the
>  related files to the directory.
> 
> [1/2] This Patch (Move DOMMatrix related files to geometry folder)
> [2/2] https://codereview.chromium.org/2709763004/ (Make WebKitCSSMatrix an
>  alias of DOMMatrix.)
> 
> BUG=581955
> 
> Review-Url: https://codereview.chromium.org/2741723005
> Cr-Commit-Position: refs/heads/master@{#459398}
> Committed: https://chromium.googlesource.com/chromium/src/+/73f22088eb2c94df42edd55abd9cf1e345e18e7c

TBR=dominicc@chromium.org,foolip@chromium.org,jinho.bang@samsung.com,esprehn@chromium.org,gogag2@gmail.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581955

[melandory, 2017-03-24 13:26:13]

The CQ bit was checked by melandory@chromium.org

[melandory, 2017-03-24 13:26:14]

Created Revert of Move geometry interface files to geometry directory.

[commit-bot: I haz the power, 2017-03-24 13:26:39]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[zino, 2017-03-24 13:31:05]

On 2017/03/24 13:26:39, commit-bot: I haz the power wrote:
> CQ is trying da patch. Follow status at
>  
>
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

lgtm

[commit-bot: I haz the power, 2017-03-24 13:31:46]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490361973911310, "parent_rev":
"9ed6f857a700f5a9cda4513050e1f908628ade10", "commit_rev":
"a3f8fd183b59f68afba5b99668cae20e7d26e330"}

[commit-bot: I haz the power, 2017-03-24 13:36:36]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-24 13:36:38]

Prior attempt to commit was detected, but we were not able to check whether the
issue was successfully committed. Please check Git history manually and re-check
CQ or close this issue as needed.

[melandory, 2017-03-24 13:40:44]

The CQ bit was checked by melandory@chromium.org

[commit-bot: I haz the power, 2017-03-24 13:40:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-24 13:41:43]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-24 13:41:45]

Failed to apply patch for third_party/WebKit/Source/core/BUILD.gn:
While running git apply --index -p1;
  error: patch failed: third_party/WebKit/Source/core/BUILD.gn:178
  error: third_party/WebKit/Source/core/BUILD.gn: patch does not apply

Patch:       third_party/WebKit/Source/core/BUILD.gn
Index: third_party/WebKit/Source/core/BUILD.gn
diff --git a/third_party/WebKit/Source/core/BUILD.gn
b/third_party/WebKit/Source/core/BUILD.gn
index
de74744c96dd7f77242a3fb7036931705dab760d..d670e354110e2a66507a8d972d96c62b152f94a8
100644
--- a/third_party/WebKit/Source/core/BUILD.gn
+++ b/third_party/WebKit/Source/core/BUILD.gn
@@ -178,7 +178,6 @@
     "//third_party/WebKit/Source/core/events",
     "//third_party/WebKit/Source/core/fileapi",
     "//third_party/WebKit/Source/core/frame",
-    "//third_party/WebKit/Source/core/geometry",
     "//third_party/WebKit/Source/core/html",
     "//third_party/WebKit/Source/core/imagebitmap",
     "//third_party/WebKit/Source/core/input",
@@ -1164,6 +1163,7 @@
     "dom/AttrTest.cpp",
     "dom/CSSSelectorWatchTest.cpp",
     "dom/DOMImplementationTest.cpp",
+    "dom/DOMMatrixTest.cpp",
     "dom/DocumentStatisticsCollectorTest.cpp",
     "dom/DocumentTest.cpp",
     "dom/DocumentUserGestureTokenTest.cpp",
@@ -1222,7 +1222,6 @@
     "frame/csp/ContentSecurityPolicyTest.cpp",
     "frame/csp/MediaListDirectiveTest.cpp",
     "frame/csp/SourceListDirectiveTest.cpp",
-    "geometry/DOMMatrixTest.cpp",
     "html/AutoplayUmaHelperTest.cpp",
     "html/FormDataTest.cpp",
     "html/HTMLDimensionTest.cpp",

[dgn, 2017-03-24 14:01:46]

There is a message on the bug about this CL landing and it also appears in
gitiles. But it's not marked as landed here. What is the actual status? How was
the merge conflict resolved?

[melandory, 2017-03-24 14:03:47]

On 2017/03/24 14:01:46, dgn wrote:
> There is a message on the bug about this CL landing and it also appears in
> gitiles. But it's not marked as landed here. What is the actual status? How
was
> the merge conflict resolved?

It's landed as a3f8fd183b59f68afba5b99668cae20e7d26e330, no manual conflict
resolution was made

[zino, 2017-03-24 14:04:11]

On 2017/03/24 14:01:46, dgn wrote:
> There is a message on the bug about this CL landing and it also appears in
> gitiles. But it's not marked as landed here. What is the actual status? How
was
> the merge conflict resolved?

I've just checked that it is landed successfully in latest source.

[esprehn, 2017-04-07 00:15:43]

esprehn@chromium.org changed reviewers:
- esprehn@chromium.org