As for a file with just extension functions, based on the Source files organization section in the docs, you should not create files like this:
Avoid creating files just to hold all extensions of some class.
Instead you should either put the extensions with the class they extend or in the client of them.
I personally think this guideline overlooks a pretty fundamental use case: extension functions for classes not owned by you with multiple clients. Also extension functions that have dependencies on classes you don't want to introduce in the module where the extended class is.
In this case it might be good to give a meaningful name instead of FooExt.kt
(if all these extension functions have a common purpose). If they don't, it might not make sense to keep them all in the same file. I'm referring to the Source file names guideline where it states:
If a file contains multiple classes, or only top-level declarations, choose a name describing what the file contains, and name the file accordingly.