fix(nextcloud_test): Skip CSRF token requests in fixtures

[provokateurin]

Needed for #1901

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 30.92%. Comparing base (85c8071) to head (f3bdd04).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2293   +/-   ##
=======================================
  Coverage   30.92%   30.92%           
=======================================
  Files         265      265           
  Lines       96710    96710           
=======================================
  Hits        29907    29907           
  Misses      66803    66803           

Flag	Coverage Δ		*Carryforward flag
cookie_store	90.51% <ø> (ø)		Carriedforward from 85c8071
dynamite	31.10% <ø> (ø)		Carriedforward from 85c8071
dynamite_end_to_end_test	60.03% <ø> (ø)		Carriedforward from 85c8071
dynamite_runtime	85.40% <ø> (ø)		Carriedforward from 85c8071
neon_dashboard	96.20% <ø> (ø)
neon_framework	45.90% <ø> (ø)
neon_notifications	100.00% <ø> (ø)
neon_talk	98.18% <ø> (ø)
nextcloud	27.67% <ø> (ø)
sort_box	90.90% <ø> (ø)		Carriedforward from 85c8071

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

[Leptopoda]

Why exactly is this needed?

[provokateurin]

This messes with the order of tests, since we only acquire a token once. This means the request is only present in the fixture of the first test that runs. Now if the order is changed (e.g. using a random seed) the fixtures will fail.