This PR aims to fix the issues raised in the following #5 (comment)

In general, we need to get to a state where the text nodes are inside of elements that have dir='auto' attribute. This allows the browser to detect the text direction.

If the text is composed of multiple parts (typically a translation with parameters), each of the parts needs to be separated in element. This is however out of scope for Stardust and should be handled in the i18n layer of the application.

Requirements:

• use Text component to render any text inside of standard Stardust components - NOTE: this is reworked in a different way, by providing rtlProps in the renderComponent function which currently contains only {dir: 'auto'} if the children or content in the component are plain string. In the future we may reworked this in a similar way the accessibility are defined, by adding slots and applying these props in different parts of the component
• Text component renders <span dir='auto>{content} if the type of content is a string
  if user provides HTML/React nodes as an input for the component content, the user is responsible for adding dir='auto' by himself. This needs to be documented
• revisit applying of truncateStyle in buttonStyles.ts - it needs to be applied even if the content contains or other elements - NOTE: This was broken by one of the latest change sin the factories - if there is children inside the factory it is returning just the element provided there.