chore: update displayed version of tokens library

Signed-off-by: Pierre-Yves Lapersonne <[email protected]>

Author: pylapp

DesignToolbox/DesignToolbox/Utils/Bundle+extension.swift

@@ -68,7 +68,7 @@ extension Bundle {
     }
 
     var tokensLibraryVersion: String {
-        "Tokens version: 0.6.2"
+        "Tokens version: 0.7.0"
     }
 
     // MARK: Private Implementation

OUDS/Core/Themes/Orange/Sources/Values/ComponentTokens/OrangeTheme+ListItemComponentTokens.swift

@@ -16,7 +16,7 @@ import OUDSTokensComponent
 import OUDSTokensRaw
 import OUDSTokensSemantic
 
-// 🧱 Tokens version: 0.6.2
+// 🧱 Tokens version: 0.7.0
 // 🤖 Generated by Tokenator
 
 extension OrangeThemeListItemComponentTokensProvider: ListItemComponentTokens {

OUDS/Core/Themes/Orange/Sources/Values/ComponentTokens/OrangeTheme+SelectComponentTokens.swift

@@ -16,7 +16,7 @@ import OUDSTokensComponent
 import OUDSTokensRaw
 import OUDSTokensSemantic
 
-// 🧱 Tokens version: 0.6.2
+// 🧱 Tokens version: 0.7.0
 // 🤖 Generated by Tokenator
 
 extension OrangeThemeSelectComponentTokensProvider: SelectComponentTokens {

OUDS/Core/Tokens/ComponentTokens/Sources/_OUDSTokensComponent.docc/OUDSTokensComponent.md

@@ -7,7 +7,7 @@ They can be seen as a kind of bridge between components and in the end primitive
 
 <!-- NOTE: Do not forget to update tokens version -->
 ```
-🧱 Tokens version: 0.6.2
+🧱 Tokens version: 0.7.0
 ```
 
 Thus if a component need to change for example its _background color_, and if a _component token_ is used for it, then only the value of this _token_ should be changed without any modification on the _component_ definition.

OUDS/Core/Tokens/RawTokens/Sources/_OUDSTokensRaw.docc/OUDSTokensRaw.md

@@ -6,7 +6,7 @@ _Raw tokens_ are smallest _tokens_ possible. They are associated to raw values a
 
 <!-- NOTE: Do not forget to update tokens version -->
 ```
-🧱 Tokens version: 0.6.2
+🧱 Tokens version: 0.7.0
 ```
 
 In fact, we choose to use as most as possible primitive types for raw values, like `Int`, `Double`, `CGFloat` or `String` so as to handle the smallest types with few impacts on the memory for ecodesign principles. Indeed with hundreds of raw tokens, it will be more efficient to store primitive small types than Swift `struct` or `class` objects. Keeping primitive types helps today to expose objects using Objective-C runtime.

OUDS/Core/Tokens/SemanticTokens/Sources/_OUDSTokensSemantic.docc/OUDSTokensSemantic.md

@@ -7,7 +7,7 @@ They can be seen as an high level of usage with functional meanings.
 
 <!-- NOTE: Do not forget to update tokens version -->
 ```
-🧱 Tokens version: 0.6.2
+🧱 Tokens version: 0.7.0
 ```
 
 If we need for example to change a warning color for a button (which has its component tokens, see [OUDSTokensComponent](https://ios.unified-design-system.orange.com/documentation/oudstokenscomponent/)), supposing this color is defined as a _semantic token_, we only have to change its assigned value and all components using the _semantic token_ won't be impacted in their definition. In fact, semantic tokens are here to bring meaning, semantic, between raw values and components.