changed port array to store based on id

[brizzbuzz]

Checklist

• The code has been run through pretty yarn run pretty
• The tests pass on CircleCI
• You have referenced the issue(s) or other PR(s) this fixes/relates-to
• The PR Template has been filled out (see below)
• Had a beer/coffee because you are awesome

What?

In reference to #724 I think it is unwise to store ports based on a user provided name, as this can easily create clashes. The unique ID is a less opinionated choice

Why?

Well, personally I think I lost a couple hairs on my head because of this, hopefully this will prevent future hair loss :D

How?

Changed addPort and a couple other methods to store/pull ports based on ID instead of name

Feel good image:

[dylanvorster]

At a surface level this looks like a small change, but this would needs further testing preferably with the community to make sure things still work. Projects that already extend from this might make use of the internal behaviour that is now changing and thus might require a rework.

[brizzbuzz]

Understandable, happy to leave it open and see where it goes... The workaround is rather simple, I just added another field that is my "name name" and then just make the "port name" unique :D Obviously not ideal but it'll do

[adaladam]

this one is related to pull request #663