feat(web2): Wpa enterprise EAP-TLS certificate support frontend

[GregoryIvo]

This PR adds front-end support for: #4872

Note: We are using the Conventional Commits convention for our pull request titles. Please take a look at the PR title format document for the supported types and scopes.

Brief description of the PR. [e.g. Added null check on object to avoid NullPointerException]

Related Issue: This PR fixes/closes {issue number}

Description of the solution adopted: A more detailed description of the changes made to solve/close one or more issues. If the PR is simple and easy to understand this section can be skipped

Screenshots: If applicable, add screenshots to help explain your solution

Manual Tests: Optional description of the tests performed to check correct functioning of changes, useful for an efficient review

Any side note on the changes made: Description of any other change that has been made, which is not directly linked to the issue resolution [e.g. Code clean up/Sonar issue resolution]

[GregoryIvo]

V1 Web UI

I am now testing to see if dropdowns with key stores are possible now.

[GregoryIvo]

Almost ready for review:
Just need to add a default password value

[mattdibi]

Tested this at d4d9c2e in #4872. Looking good so far!

@GregoryIvo one question: do we really need two different fields for passing the client key if they are the same?

... or did I do something wrong?

[GregoryIvo]

This is correct, and expected. I was thinking about that too but am torn because I like the potential flexibility

[mattdibi]

This is correct, and expected. I was thinking about that too but am torn because I like the potential flexibility

As a user I find it confusing... Why should I set the same for both if I added it as a single Pub/Priv key pair? Also I have a hard time imagining a situation in which this flexibility could be taken advantage of? Can you explain to me a scenario where these two separated fields can be useful? 🤔

[mattdibi]

Superseded by #4895