Docs: Initial sequence of pages in Documentation

[AdarshRawat1]

What

Reordered the sequence of topics in generated documentation. View mockup for Changes live here

Removed following outdated pages from documentation, until they are updated.

• https://github.com/p4lang/p4c/blob/main/backends/p4tools/cmake/README.md
• https://github.com/p4lang/p4c/blob/main/backends/p4tools/common/lib/README.md
• https://github.com/p4lang/p4c/blob/main/backends/p4tools/common/README.md
• https://github.com/p4lang/p4c/blob/main/backends/p4tools/modules/testgen/lib/README.md

Why

Updated sequence of files listed by Doxygen output based on discussion in

• Question on order of files listed by doxygen output #4746

Extra Reference

Current Sequence

List
P4C
Repository
Revision History
Overview
P4 Compiler Intermediate representation
Behavioral Model Backend
DPDK backend
PSA implementation for eBPF backend
eBPF Backend
Graphs Backend
p4fmt (P4 Formatter)
P4test Backend
P4Tools CMake
P4Tools Common Library Code
P4Tools Common C++ code
P4Tools Contributors
README
P4Testgen Benchmarks
P4Testgen Library
P4Testgen
P4Testgen BMv2 target tests
P4Tools - Testing Tools For P4 Targets
TC backend
uBPF Backend test programs
Introduction to uBPF Backend
uBPF Backend testing
Common P4C utility functions
P4C Intermediate Representation (IR) Classes
Changelog
Deprecated List
Todo List
Topics
Namespaces
Classes

Updated Sequence LIVE

List
P4C
Repository
Revision History
Overview
P4 Compiler Intermediate representation
Common P4C utility functions
P4C Intermediate Representation (IR) Classes
Changelog
Behavioral Model Backend
DPDK backend
eBPF Backend
PSA implementation for eBPF backend
Graphs Backend
p4fmt (P4 Formatter)
P4test Backend
P4Tools - Testing Tools For P4 Targets
P4Tools Contributors
README
P4Testgen
P4Testgen Benchmarks
P4Testgen BMv2 target tests
TC backend
Introduction to uBPF Backend
uBPF Backend test programs
uBPF Backend testing
Deprecated List
Todo List
Topics
Namespaces
Classes

[jafingerhut]

LGTM

[jafingerhut]

@fruffy It appears DCO is required in order to click the Merge button on Github. Note: That sounds GOOD to me. Just wanted to let you know, since you mentioned recently that you thought it was optional right now.

@AdarshRawat1 I think the only thing needed to commit this is for you to add DCO. You can can click the "Details" link to the right of the failing check labeled "DCO" for instructions on how.

[fruffy]

@fruffy It appears DCO is required in order to click the Merge button on Github. Note: That sounds GOOD to me. Just wanted to let you know, since you mentioned recently that you thought it was optional right now.

I think this is because this is a draft pull request.

[AdarshRawat1]

@AdarshRawat1 I think the only thing needed to commit this is for you to add DCO. You can can click the "Details" link to the right of the failing check labeled "DCO" for instructions on how.

Thanks, Done !!

[jafingerhut]

I was wrong. You also need to change the PR so it is no longer in Draft status.

[AdarshRawat1]

I'm just testing to see if anything breaks or is not being rendered. [The list of classes and namespaces].

[fruffy]

Seems like this PR has broken CI, I would use rebase merge instead of conventional merging. It works much better on Github.