Remove LJC codesign certs from all machines

[gdams]

We no longer need these codesign certs. The safest option is to fully remove them from the machines to prevent us signing an Adoptium build with the wrong cert

Checklist

• commit message has one of the standard prefixes
• FAQ.md updated if appropriate
• other documentation is changed or added (if applicable)
• playbook changes run through VPC or QPC (if you have access)
• for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

[sxa]

Happy with this in principle but it might be worth waiting until we're a little further down the Adoptium route before merging and deploying. We should also verify whether this will impact other teams using our stuff as we wouldn't want to risk destabilising others that might be relying on those certificates. Tagging @AdamBrousseau (I'm not sure if you're using any of the signing mechanisms that will be affected by this) for a review before accepting this change

[AdamBrousseau]

Thanks for the heads up Stewart. After review I think we should be fine with this change. We use a different mechanism now to sign our mac & win builds.

[karianna]

Vagrant run is erroring on:

/opt/vagrant/embedded/gems/2.2.16/gems/vagrant-2.2.16/lib/vagrant/patches/net-ssh.rb:10:in rsa_compat_build_request': undefined method []' for nil:NilClass (NoMethodError)

[Haroon-Khel]

The vagrant failure is on the Solaris check. I wouldnt think it would be associated with this pr. Either way, ive kicked off another job

[sxa]

The vagrant failure is on the Solaris check. I wouldnt think it would be associated with this pr. Either way, ive kicked off another job

@Haroon-Khel What was the other job? Was it a re-run of the Solaris check or something else?

[Haroon-Khel]

@Haroon-Khel What was the other job? Was it a re-run of the Solaris check or something else?

@sxa A re run of the Solaris check. It still fails with the same error. As discussed in Slack, we agreed that the failure does not concern this pr. Is it safe to merge then?

[gdams]

I'd say this is safe to merge. @sxa please approve and merge