ui: bump UI pkg version to match CloudStacks

[yadvr]

This uses the version in UI's package.json same as CloudStack's. The idea is that static assets aren't cached per discussion on #7546

Fixes #7546

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

[yadvr]

@blueorangutan ui

[blueorangutan]

@rohityadavcloud a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

[yadvr]

This could need a manual UI upgrade test; say from 4.18.0 or 4.18 without this PR to this PR/pkgs.

[weizhouapache]

@blueorangutan package

[blueorangutan]

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

[codecov]

Codecov Report

Merging #7894 (e890000) into 4.18 (db0e7a6) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               4.18    #7894      +/-   ##
============================================
- Coverage     13.06%   13.06%   -0.01%     
+ Complexity     9084     9083       -1     
============================================
  Files          2720     2720              
  Lines        257289   257289              
  Branches      40116    40116              
============================================
- Hits          33612    33610       -2     
- Misses       219455   219458       +3     
+ Partials       4222     4221       -1     

see 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[blueorangutan]

Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 6855

[DaanHoogland]

code looks good, I'll find a random version to (test) upgrade from

[DaanHoogland]

did an upgrade from 4.17.1 and monkey tested the resulting env. No strangeties encountered. Do you think I should do a more structured test for this @rohityadavcloud @weizhouapache @Others ?

[weizhouapache]

did an upgrade from 4.17.1 and monkey tested the resulting env. No strangeties encountered. Do you think I should do a more structured test for this @rohityadavcloud @weizhouapache @Others ?

fine with me @DaanHoogland

have you verified #7546 ?

[DaanHoogland]

have you verified #7546 ?

@weizhouapache I see new strings in comparison to 4.17.1 :

if that is what you mean?

[weizhouapache]

have you verified #7546 ?

@weizhouapache I see new strings in comparison to 4.17.1 : if that is what you mean?

looks good, :+1

[weizhouapache]

code lgtm