Option #2 is the way I'd go.
When thinking about the Angular 2 components, I consider them to be a single entity, made up of multiple files. You don't move your HTML / CSS files out to some other directory, away from the component, so why move the unit tests?
I've written a small utility plugin for VSCode that I personally find quite useful - it compresses an Angular 2 component into a single entry on the Explorer view, and adds icons / context menu options for getting to the template / css / unit tests. This helps me see the component as a single unit, comprising multiple parts. Maybe something like that would help keep your directory "clean" if that's what you worry about?
I would encourage you to think about unit tests as PART OF your code, rather than in addition to. They'll be very useful if you can keep on top of them.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…