If my understanding is correct, when flang was added to llvm-project, it was separated from the other llvm projects (which are all handled in a list called LLVM_ALL_PROJECTS) because it had a higher C++ requirement (C++17 instead of C++11). Supposedly, this discrepancy has since been resolved and flang should be safe to be add to this list. From my testing this seems to have worked without any issues, but I am opening this up to the community to discuss if there are any issues with this move or if this change is wanted.
The motivation for doing this move now is the recent discussions about better supporting Flang's runtime libraries with existing LLVM runtime infrastructure. As a prerequisite, before we can consider stuff like adding flang's runtime to LLVM_ENABLE_RUNTIMES=all, it would make sense to first treat flang like one of "all the llvm projects" (if this can be done without issue)
Might be useful to keep the LLVM_EXTRA_PROJECTS here and below, even if empty for now? Adding a new project to LLVM could then just reuse this.