fix: list should have unique "key" in web application page

[hongky-1994]

What this PR does:
Fix error log in console web

• Child in a list should have unique "key" (Application list page)
  

Why we need it:

• To make web console clean and prevent unwanted behavior

Which issue(s) this PR fixes:

• None

Does this PR introduce a user-facing change?:
No

• How are users affected by this change: None
• Is this breaking change: No
• How to migrate (if breaking change): None

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.29%. Comparing base (e0dfc18) to head (b1c1d1c).
Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5502   +/-   ##
=======================================
  Coverage   26.28%   26.29%           
=======================================
  Files         464      464           
  Lines       49624    49626    +2     
=======================================
+ Hits        13043    13047    +4     
+ Misses      35547    35546    -1     
+ Partials     1034     1033    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[t-kikuc]

[ASK]
v.version is already used in L178. Is that OK?

(I'm sorry, but I'm not familiar with React)

[hongky-1994]

Thanks for asking,

Yes, @t-kikuc it is the same key for 1 record when map from recentlyDeployment.versionsList.

The error show that we need uniq key for each child when map from recentlyDeployment.versionsList so I use v.version as uniq key.

[t-kikuc]

@hongky-1994 Thank you! got it.

[Warashi]

Thank you!
Is the v.version the v0.6.0 of the screenshot below?

This column sometimes contains multiple artifacts and may contain different artifacts with the same version.
So, I think it's a bit risky to use v.version as the unique key.

[hongky-1994]

Thank @Warashi !
I update the pull with key ${v.name}:${v.version}

The key is just needs to be unique in a single cell, so the name and version of artifacts in a single row must be different, right?

[Warashi]

Thanks @hongky-1994 !

the name and version of artifacts in a single row must be different, right?

Yes, I think so. The combination of name and version is safe as a unique key in a single row.

[Warashi]

LGTM

[khanhtc1202]

👍