EPIC - Update TabView to have Context

[tuliopereirazup]

Description

Since we have launched Communication between Components (#54), we can now update TabView to simplify its implementation, and to allow new ways to use it on different use cases.

Ex1: use a TabView that the bar would be at the bottom, and the scroll of "pages" would be at the top

Ex2: when there is some change on current displayed "tab", I wanted to trigger an analytics event

Possible Solution

• deprecate TabView and TabItem (and others related classes if needed)
• create a new TabBar component that will be just the view with a list of tabs.
  • current selected tab should be an expression
  • when some tab is selected, trigger an event
  • try to use it with PageView, to see if this new composition can be used instead of the old TabView
• update documentation accordingly

Maybe problematic points

• TabView currently have some animations for its selected tab, and for the scroll of pages

• Web Update TabView to have Context beagle-web-components#7

• iOS: try to see this as well Wrong scroll past the last tab #491

• Android Android - Update TabView to have Context #598

[yandiaszup]

Models:

struct TabBar {
    public let children: [TabBarItem]
    public let styleId: String?
    public let currentTab: Expression<Int>?
    public let onTabSelection: [RawAction]?
}

public struct TabBarItem {
    public let icon: String?
    public let title: String?
}

[yandiaszup]

The idea its to use this TabBar component with PageView, communicating then with context and expressions to replicate TabView component behavior so we can deprecate it.

[carolinegoncalveszup]

This change also request pageview contract to be changed.
For the expected behavior on the web we should add showArrow in pageview which is a boolean. This prop will be used to indicate if the pageview arrows that are shown on the web should or not be visible.

[carolinegoncalveszup]

For the tabview component we suggest:

struct TabBar {
    public let items: [TabBarItem]
    public let styleId: String?
    public let currentTab: Expression<Int>?
    public let onTabSelection: [RawAction]?
}

public struct TabBarItem {
    public let icon: ImagePath?
    public let title: String?
}

The tabItem array should not be children as it is not a ServerDrivenComponent, so we suggest items instead.
Another suggestion is to change the icon type to ImagePath, in which the _beagleImagePath_ must always be local