fix(psalm): Fix all @throws annotations and add missing ones

[provokateurin]

No description provided.

[come-nc]

I kind of hate that Exception is sometimes \Exception and sometimes \OCP\DB\Exception. I tend to never use Exception because of that to make it clear when we throw the root one.

Also @throws blocks should contain an explanation when the exceptions is thrown, except for self-explanatory ones like NoUserException and InvalidArgumentException.

And for all methods implementing an OCP interface they should not throw unless it’s permitted by the interface. But that does mean for some of them we should modify the interface instead.
For controllers I do not know the policy, are they allowed to throw, and which kind of exceptions/throwable is handled by Nextcloud core?

[come-nc]

When does that throw Throwable? For me that should never be documented, Throwable which are not Exception are bugs to be fixed, not documented. Anything can throw a Throwable if you use it wrong.
Would also be good if those @throws tag would include a description of when to expect a throw.

[come-nc]

Should be caught inside, this method is not documented as throwing in ICapability and should not throw.

[come-nc]

when? Add a description please

[come-nc]

Suggested change

	/**
	* @throws LogicException
	*/
	public function __construct() {
	parent::__construct();
	}

dead code