Culture update process

1. First after writing code and making html and labels, write labels with "keys".

2. values of those culture keys is provided in en-US.json at root of that

component.

3. after updating that value, run command "npx orxe-culture", this will update the
other 2 files with upload.

4. Now when we are runnig or debugging the app/component using requestly, when we
load the component/app in a microapp as it loads the UI that is
already deployed so change the import path of component to local path in your
microapp so that it will pick your local component and do same environment.ts
step as did in requestly debug steps.

5. Once done, to load the Culture on env to see the changes, open postman----Pick
the scopeID from the en-US calls from network tab from its URL
It will look like this -----> "1389_activity_compname"

6. First copy culture from upload folder of that component.

7. GET culture of that scope it through hitting through Postman. Check whether
culture exist. If not then...

8. Click Upload, then update URL with correct scopeID, and until batch comes []

9. then publish on stage.....then on live.....then again get.....it will show now.

10. Now culture is published to stage........QA automatically reads from there.