Undeprecate resources

[danburonline]

Fixes #4509

Description

Major things

• Added an undo deprecate button to the ResourceView component. When clicking on it it updates the states and goes to the latest revision (it's the same flow as when you, e.g. deprecate a resource).
  
• Don't show the undo deprecation button if it's an older resource revision.
• Added a toast/notification in case the un-deprecation failed
  
• Don't allow undoing deprecation for unsupported resource types. Example:
  . This would need to be changed as soon as we allow the deprecation of other resource types as well.
• Hide the button to deprecate the default Elasticsearch view, because it would break the listing operations (as described by @imsdu):
  

Cleaning

• Sorted the package.json via sort-package-json => following common rules.
• • Unit tests failed after my adjustments as the QueryClient was missing. This is fixed.
• Sorted imports of files I worked at. The ESLint rule is still missing (or generally ESLint).
• Replaced the bitmap logo with an SVG.
• Worked on reducing the delta from design to code by adjusting the logo size and the main white spaces on the pages. See the screenshot below for a before and after:

Additional Tickets Uncovered

• 4541: The test coverage fell due to my adjustments. But to add new tests for the ResourceViewContainer component. This was out of scope for the the current ticket of this PR (#4509)
• 4542: During the development I realised that the UI is quite messy, as it potentially grew organically (Frankenstein UI). This new ticket discusses a potential non-functional redesign.
• 4543: During the development, I realised that the copy of the app was not consistent and, in general, maybe sometimes too technical/not conforming the docs and/or the mental model of Nexus. This new ticket discusses this.

How has this been tested?

• Current tests pass.
• Tested the flows locally via prod build.
• I added an E2E test that tests the happy-path flow of deprecating a deprecatable resource. If I should add more E2E tests, let me know. I think the other non-happy paths can be tested via unit tests (as mentioned in 4541).

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• I have updated the documentation accordingly.
• I have added necessary unit and integration tests.
• I have added screenshots (if applicable), in the comment section.

[codecov-commenter]

Codecov Report

Attention: 20 lines in your changes are missing coverage. Please review.

Comparison is base (de04188) 48.08% compared to head (cfa3fdc) 48.05%.
Report is 1 commits behind head on develop.

Files	Patch %	Lines
src/shared/containers/ResourceViewContainer.tsx	66.03%	18 Missing ⚠️
src/shared/containers/ResourceActionsContainer.tsx	77.77%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1438      +/-   ##
===========================================
- Coverage    48.08%   48.05%   -0.04%     
===========================================
  Files          249      249              
  Lines        11368    11390      +22     
  Branches      2655     2665      +10     
===========================================
+ Hits          5466     5473       +7     
- Misses        5869     5883      +14     
- Partials        33       34       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bilalesi]

good work, left some comments

regarding this part:
BlueBrain/nexus#4542: During the development I realised that the UI is quite messy, as it potentially grew organically (Frankenstein UI). This new ticket discusses a potential non-functional redesign.

There is already a design for the Resource details view and we already have a ticket for that
I will share it with you when we get there

[danburonline]

@bilalesi I see that the tests are still failing (or sometimes fail and sometimes not). Will investigate before merging this.