chore(*): Update versions to not be static. Update contributing.

Author: skrustev

.github/CONTRIBUTING.md

@@ -94,14 +94,14 @@ There are several ways to localize components' string resources:
     1.1. Localize a given instance of component - each component which supports localization has input property `resourceStrings`. Setting a newly instantiated object to this property will localize only that given component's instance.
     1.2. Localize all resources for a component type - each component which supports localization has input property `resourceStrings`. To localize all instances of a given component in the application the following steps should be performed - get the value of the input property `resourceStrings` of the component to be localized; do not create a new instance but replace the existing strings within the object. By default all components of a given type in an application share one instance of the resource strings. Replacing a value in that instance affects all components of that type in the application.
     1.3. Localize all resources for all components - use global method `getCurrentResourceStrings` to get an object containing current resource strings for all components. To provide localized resources just pass an object of type `IResourceStrings` to the global method `changei18n`.
-    1.4 As of 20.2.0 the localization has new implementation and you can use the new API `registerI18n` to register resource string for a component or all components for the whole app, as well as which locale it corresponds to. To localize a single component you will need to get is corresponding resource string keys using one of the available resources and provide only those keys.
+    1.4 As of 21.1.x the localization has new implementation and you can use the new API `registerI18n` to register resource string for a component or all components for the whole app, as well as which locale it corresponds to. To localize a single component you will need to get is corresponding resource string keys using one of the available resources and provide only those keys.
 
 2. Using npm package:
 We've created new repository which will hold the resource strings for languages different than English:
 https://github.com/IgniteUI/igniteui-angular-i18n 
 
 **NOTE** The localization repo has been moved to live inside the `igniteui-angular` repository under `./projects/igniteui-angular-i18n`
-**NOTE** As of 20.1.x the localization resource strings have been moved to the [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n) repository under `projects/igniteui-i18n-resources`.
+**NOTE** As of 21.1.x the localization resource strings have been moved to the [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n) repository under `projects/igniteui-i18n-resources`.
 
 A npm package should be published each time we release new version of Ignite UI for Angular. Its version should correspond to the version of the igniteui-angular npm package.
 One could localize an application by importing the corresponding localized resource strings from the localization package (`igniteui-angular-i18n`) and use the methods described in the previous bullet to localize the whole application or part of it.

package-lock.json

@@ -76,7 +76,7 @@
     "dompurify": "^3.3.0",
     "express": "^5.2.1",
     "fflate": "^0.8.1",
-    "igniteui-i18n-core": "1.0.1",
+    "igniteui-i18n-core": "^1.0.1",
     "igniteui-theming": "^24.0.0",
     "igniteui-trial-watermark": "^3.1.0",
     "jspdf": "^3.0.4",

package.json

@@ -24,7 +24,7 @@
   },
   "homepage": "https://github.com/IgniteUI/igniteui-angular/projects/igniteui-angular-i18n#readme",
   "dependencies": {
-    "igniteui-i18n-core": "1.0.1",
-    "igniteui-i18n-resources": "1.0.1"
+    "igniteui-i18n-core": "^1.0.1",
+    "igniteui-i18n-resources": "^1.0.1"
   }
 }

projects/igniteui-angular-i18n/package.json

@@ -76,7 +76,7 @@
         "jspdf": "^3.0.2",
         "lodash-es": "^4.17.21",
         "igniteui-theming": "^24.0.0",
-        "igniteui-i18n-core": "1.0.1",
+        "igniteui-i18n-core": "^1.0.1",
         "@igniteui/material-icons-extended": "^3.1.0"
     },
     "peerDependencies": {