feat(neon_http_client): Add AuthenticationInterceptor

[provokateurin]

Closes #365

Quite simple to implement with our interceptors 😄

Every Account gets it's own NeonHttpClient and therefore it's own AuthenticationInterceptor, so no separation is required.

I removed the catch handlers because the interceptor needs to be able to throw an exception for requests that need to be blocked.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.94%. Comparing base (ac73ec9) to head (114487b).
Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2454      +/-   ##
==========================================
+ Coverage   29.92%   29.94%   +0.02%     
==========================================
  Files         332      333       +1     
  Lines      124414   124456      +42     
==========================================
+ Hits        37231    37273      +42     
  Misses      87183    87183              

Flag	Coverage Δ		*Carryforward flag
account_repository	99.64% <ø> (ø)
cookie_store	99.48% <ø> (ø)		Carriedforward from ac73ec9
dashboard_app	96.05% <ø> (ø)
dynamite	31.08% <ø> (ø)		Carriedforward from ac73ec9
dynamite_end_to_end_test	61.69% <ø> (ø)		Carriedforward from ac73ec9
dynamite_runtime	85.40% <ø> (ø)		Carriedforward from ac73ec9
neon_dashboard	96.05% <ø> (ø)		Carriedforward from ac73ec9
neon_framework	43.65% <ø> (ø)
neon_http_client	94.76% <100.00%> (+1.47%)	⬆️
neon_notifications	100.00% <ø> (ø)		Carriedforward from ac73ec9
neon_talk	99.45% <ø> (ø)		Carriedforward from ac73ec9
nextcloud	25.90% <ø> (ø)
notifications_app	100.00% <ø> (ø)
sort_box	90.90% <ø> (ø)		Carriedforward from ac73ec9
talk_app	99.09% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Files with missing lines	Coverage Δ
...rceptors/authorization_throttling_interceptor.dart	100.00% <100.00%> (ø)
...ges/neon_http_client/lib/src/neon_http_client.dart	96.49% <100.00%> (+0.49%)	⬆️

[provokateurin]

I'm not so happy with the name of the interceptor, let me know if there is something more fitting.

[Leptopoda]

Did you test that this also work together with the nextcloud package?
I think 401 responses are thrown so the response interceptor wouldn't ever be used.

[provokateurin]

Did you test that this also work together with the nextcloud package?
I think 401 responses are thrown so the response interceptor wouldn't ever be used.

You're thinking on the wrong layer. The response interceptor comes way before the response is parsed in the nextcloud package and an exception might be thrown.

[provokateurin]

Maybe UnauthorizedInterceptor is a better name?

[Leptopoda]

You're thinking on the wrong layer. The response interceptor comes way before the response is parsed in the nextcloud package and an exception might be thrown.

Yep. I mixed something up in my head.

Maybe UnauthorizedInterceptor is a better name?

I'm not sure about the naming and don't have any opinion on it. What about CheckAuthenticationInterceptor?

[provokateurin]

I'm not sure about the naming and don't have any opinion on it. What about CheckAuthenticationInterceptor?

It still doesn't really convey what it is doing. I think something like UnauthorizedThrottlingInterceptor describes the functionality the best way, but it is still not intuitive. Maybe there simply is no good name for it.