[KeyVault Certificates] v4.0.2 hotfix for #9005 and #9020

[sadasant]

This PR updates @azure/keyvault-certificates to version 4.0.2. It includes a fix for the issue #9005, which consists in ensuring that parallel requests load the already cached credentials appropriately, and a fix for the issue #9020, which consists on ensuring that the updateCertificateProperties method correctly uses the certificate attributes.

I'm using the same base branch as the one used for the previous hotfix (4.0.1): https://github.com/Azure/azure-sdk-for-js/tree/hotfix/keyvault-challengeAuth-certificates-from-4.0.0

The fixes in greater detail are:

For the issue #9005

PR to master #9059

The recent hotfix showed an outstanding bug now that the cache is working correctly: Multiple async requests running at the same time quickly fail rather than re-using the credentials of the first authenticated.

This fix ensures that anytime we receive a response that indicates that authentication is necessary we update the original request with the available credentials and send it again, even if we already had a valid token and challenge in memory.

I also refactored the logic to make it easier to follow, so that future changes can be made more straightforwardly.

For the issue #9020

PR to master #9135

The bug is that updateCertificateProperties is not correctly passing the attributes required by the underlying method.

The fix I'm making is to change the updateCertificateProperties method to correctly set the certificateAttributes in the options bag that is passed to the generated updateCertificate method:

-        this.setParentSpan(span, requestOptions)
+        {
+          ...this.setParentSpan(span, requestOptions),
+          certificateAttributes: toCoreAttributes(options)
+        }

[sadasant]

This PR is green, but I'm waiting for @xirzec 's approval on #9059

Update: That is done!

[sadasant]

/check-enforcer evaluate

[KarishmaGhiya]

/check-enforcer evaluate