layout: Combine `layout_2020` and `layout_thread_2020` into a crate called `layout` (#36613)

Now that legacy layout has been removed, the name `layout_2020` doesn't
make much sense any longer, also it's 2025 now for better or worse. The
split between the "layout thread" and "layout" also doesn't make as much
sense since layout doesn't run on it's own thread. There's a possibility
that it will in the future, but that should be something that the user
of the crate controls rather than layout iself.

This is part of the larger layout interface cleanup and optimization
that
@Looriool and I are doing.

Testing: Covered by existing tests as this is just code movement.

Signed-off-by: Martin Robinson <mrobinson@igalia.com>

1 files changed, 0 insertions, 20 deletions

diff --git a/components/layout_2020/fragment_tree/mod.rs b/components/layout_2020/fragment_tree/mod.rs
deleted file mode 100644
index 8738f2a6af7..00000000000
--- a/components/layout_2020/fragment_tree/mod.rs
+++ /dev/null
@@ -1,20 +0,0 @@
-/* This Source Code Form is subject to the terms of the Mozilla Public
- * License, v. 2.0. If a copy of the MPL was not distributed with this
- * file, You can obtain one at https://mozilla.org/MPL/2.0/. */
-
-mod base_fragment;
-mod box_fragment;
-mod containing_block;
-mod fragment;
-#[allow(clippy::module_inception)]
-mod fragment_tree;
-mod hoisted_shared_fragment;
-mod positioning_fragment;
-
-pub(crate) use base_fragment::*;
-pub(crate) use box_fragment::*;
-pub(crate) use containing_block::*;
-pub(crate) use fragment::*;
-pub use fragment_tree::*;
-pub(crate) use hoisted_shared_fragment::*;
-pub(crate) use positioning_fragment::*;