Don't force "new feature tours" onto all users

### Your use case

#### What would you like to do?

Follow my daily routine without forced interruption.

#### Why would you like to do it?

It's my job.

#### How would you like to achieve it?

When Element authors re-design the user interface, or otherwise break functionality, _ask me_ if I require hand-holding and a click-through of what is assumed to be the correct learning path. Ideally, the behavior would be opt-in, to not require me to repeat it for all of my work clients that rely on Element in their communication platforms.

### Have you considered any alternatives?

I tried to block the UI elements with uBlock Origin, but the randomized CSS class names void this approach. Additionally, the approach seems ineffective when Element is used as a PWA on Windows.

I also repeatedly closed and re-opened Element, in the hope that it would just give up and mark the exercise as completed, but it is very persistent in requiring me to hunt down and click all the **Next** buttons.

### Additional context

Anti-features like the one in question are ignored by the users that require them, and everybody else is annoyed. A UI should be designed in a way that it doesn't require this UX from returning or new users. The amount of time that is globally wasted by such choices should be considered.

The issue names no files, tests, or entry points. Start by reproducing the forced new-feature tour in Element Web and trace where the tour is triggered and its completion state is stored; done should mean users can decline or opt out without being repeatedly interrupted.

Written by the indexing model from the issue text.