I find there are some practical exceptions to the "one thing per file" rule; interfaces are a common case. Perhaps you want a simple enum that's used only in the context of that interface, or you pair an interface with its implementation as mentioned by @jlew, or in your case, perhaps a couple of simple extension methods could go in the same file. But I would move them to a separate file if the implementations get to complicated.
However, remember that extension methods are made available by importing the namespace in which they are defined. So consider the typical usage of your extension method. Perhaps there is a different namespace that is associated with the specific context in which these extension methods will be used. But if these extension methods are general purpose, it would make sense to keep them in the same namespace as the interface itself, and perhaps in the same file.