Fix/remove PHP 8.2 depreciation messages

[krytenuk]

I was getting deprecation notices after updating a project to PHP 8.2.
Have added type hints and property defaults along with a general code tidy on the worked files.

[sreichel]

Type hints are breaking changes, not?

[develart-projects]

As failing tests are suggesting, these are breaking changes, not really backward compatible. Therefore I'm against this PR to be merged.

[krytenuk]

Changed the default delimiters to null. Hopefully fixed phpunit errors.

[boenrobot]

Suggested change

	* @return bool|int
	* @return int|false

for consistency with the property.

[develart-projects]

Well, we still have tons of hints, forcing some type. Like:
public function getViewScript(?string $action = null, ?bool $noController = null): string

Why exactly we are trying to be more typed here pls? Wgat are those deprecation messages about?
By merging this, consequences could be huge in terms of backward compatibility.

[IMSoP]

My guess is this is about PHP adding "tentative return types" to built-in classes, and giving (non-error) messages like this:

Deprecated: Return type of Example::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

As the message says, the backward-compatible way of acknowledging but silencing the notice is to add a #[\ReturnTypeWillChange] attribute. If placed on its own line, this looks like a comment to older versions of PHP, so is completely safe. Note that all that does is reduce the logging of the message; the actual problem will probably have to be tackled if and when someone wants a version of this library working on PHP 9.0.

See this Stack Overflow reference question for a deeper explanation.