implemented backToTabView use case

[skrukwa]

Motivation and Context

Your Changes

Description:

Type of change (select all that apply):

• [x] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)
• [x] Refactoring (internal change to codebase, without changing functionality)
• [x] Test update (change that modifies or updates tests only)
• [x] Documentation update (change that modifies or updates documentation only)
• [x] Other (please specify):

Testing

Questions and Comments (if applicable)

Checklist

• [x] I have performed a self-review of my own code.
• [x] I have added tests for my changes.
• [x] Coverage tests
• [x] Coding style (conforms to Google Java Style Guide)
• [x] Especially follows section 7 (Javadoc is present for every public class, public or protected member)
• [x] Especially follows section 4.6 (Multiple consecutive blank lines are not encouraged)
• [x] Correctness (follows CA and SOLID, is a reasonable and not overly complicated solution, etc.)
• [x] Description of pull request is clear, consise, and reasonably detailed

[skrukwa]

Unclear how errors or exceptional cases are handled in this method. Should maybe add error handling. Should also add javadoc and comments to make code clearer. Overall good job!

changing the view will never throw an error or or have to present a failure view