I have no association with the linked project, but here are some reasons why I might take the same approach:
1. Source control. Code at the level of PG/SQL into source control isn't as easily deployed and managed as, say, Java code.
2. Not being strongly tied to a single software. It's true that this is currently directly intended to be used for PG, but keeping it separate would make it easier to re-adapt for another database software in the future.
3. Lack of expertise with PG internals. This one is just a reason, not a justification.
Note that I'm not defending any software design decisions here, just speculating in a way I find reasonable. I also have the same questions and would be curious to hear the author(s)'s responses.
(Edited for formatting issues with the numbered list - and then again for spelling errors)