katesessions/konsoleprofiles: do not hold profilesmodel on the stack
this causes crashes when accessing the kdirwatch since it doesn't get moveToThread along with the runner. i.e. the runner thread calls into a kdirwatch that lives on the gui thread. this is particularly problematic since kdirwatch is really just a facade for thread-local backing technology, so when the wrong thread calls into kdirwatch it may tap into uninitialized memory (for that thread -- it is initialized on the "correct" thread)