Support Custom Root Certificate

[NghiaTranUIT]

Description

• It's time to implement the Custom Root Certificate
• Doc: https://docs.proxyman.com/advanced-features/custom-certificates
• DO NOT Implement Client or Server Certificate. It's for the future

Acceptance Criteria

• When there is no Root Certificate (default or custom), implement this UI

• If we generate a default Root Certificate in Certificate Menu -> Install for Windows -> Manual or Auto Tab -> It will show the default certificate in the Custom Root Certificate

• Delete button is disabled if it's a Default Certificate, but enable if it's a custom Root certificate
• Able to import p12 (with passphrase) -> Decrypt p12 with password to PEM and Private Key and store in Proxyman Data Folder -> Custom Certificate Folder. Do not store user password

• Make sure it shows an error if the passphrase is wrong.

• Able to import PEM / DER (This feature is not available on macOS). This view should be separated into components, we we can reuse it later for Server / Client Certificate

• After importing custom Root Certificate -> Verify that the UI displays

Logic

• Maybe we should write new CustomCertificateService.ts to store and handle custom certificate (maybe we will use this class to store Client/Server customer certificate too)
• All custom certificates should be stored in Proxyman Data Folder -> Custom Certificate Folder
• Do not store user p12 passphare. We decrypt p12 file to PEM and Private Key.
• Write a simple func to verify if it's a valid Root Certificate. Ping @NghiaTranUIT to get the idea. If it's invalid, still import it, but show warning yellow label on the UI to warning the user
• ✅ IMPORTANT LOGIC: If Custom Root Certificate is provided -> We should clear all cache certificates (read ca.js) and know where it's store and we should clear all cache and delete old server certificate (which was issued by old Root Certificate)

[NghiaTranUIT]

How to test

1. Generate new default Root Certificate -> When doing Mitm, make sure we generate Server Certificate by using Defualt Root Certificate (It's a default behavior) -> Open Google Chrome -> Click on the Certificate issue on Toolbar -> Verify Issued By is a current Root Certificate
2. Generate a new custom certificate with a different Organization Name by command line (Read https://docs.proxyman.com/advanced-features/custom-certificates)
3. Do not delete the current certificate -> Go to Certificate Menu -> Add new Custom Root Certificate -> Add p12 -> Enter passphare -> Import success -> UI is updated with new Custom Certificate -> Make sure all old certificates are cleared
4. When making a requests on Google Chrome -> verify Issued By is from the new CUstom Root Certificate
5. When I delete a custom root certificate -> Because the default root certificate is already installed -> It show the current Root certificate -> I can intercept and decrypt HTTPS as normal (by using Default Custom Certificate)