M-x recompile command does not always relaunch the compilation process in the original buffer

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27, 28, or 29. *(Unstable versions end in .50, .60, or .9x)*

### Expected behavior

If the recompile command ('g' key) is issued in a compilation buffer, the compilation process should be executed in the same buffer , even if the buffer is renamed

### Current behavior

If a compilation buffer is not named *compilation*, issuing a recompile (M-x recompile or 'g' key) spawns another compilation buffer (named *compilation*) instead of rerunning the compilation process in the original buffer.
This is an issue when manipulating several compilation buffers with different names.
This issue does not appear if I run the same steps with emacs -q

### Steps to reproduce

1. Launch a compilation process with M-x compile
2. make XXXX
3. rename *compilation* buffer (to be able to handle different "compilations" in different directories)
C-x x r or rename-buffer

4 . Press the g key in the buffer - the compilation process does not appear in the current buffer but in another , new *compilation* buffer.

### System Information

https://pastebin.com/PPMFgz2q