feat: allow developers to choose the default view

[artemrys]

Issue number: #1041

Summary

Changes

Please provide a summary of what's being changed

Configuration page require admin privileges and if a Splunk user is not an admin - configuration page will show an error which is confusing. This PR allows to set a default page to search so there will be no error shown when a Splunk user opens add-on for the first time.

This PR enables TA developers to choose the default view, one of four: inputs, configuration, dashboard and search.

User experience

Please describe what the user experience looks like before and after this change

Nothing changes for the existing customers. For customers who decide to use search view as a default one - they need to update their globalConfig file, specifically set meta.defaultView to search and rebuild an add-on.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

[kkedziak-splunk]

LGTM but wouldn't it be better to introduce a text parameter, where one could put a name of the default view? In case someone in the future asks for e.g. inputs being default?

[artemrys]

LGTM but wouldn't it be better to introduce a text parameter, where one could put a name of the default view? In case someone in the future asks for e.g. inputs being default?

I am working on that right now.