When a property is both required and sensitive, setting it blank does not remove the "Sensitive value set" message.

When testing NIIFI-12960, I noticed when a property had the combination

.required(true)
.sensitive(true)

and after a user entered a value and then attempts to remove the value it does not work and the message "Sensitive value set" still remains in the text box. This is even when the user checks the "Set empty string" checkbox.
Attached is a screenshot of a DecryptContent processor after an attempt to remove the set password.

The combination

.required(true)
.sensitive(true)

is prevalent in the code base. I found it ~40 times in the following files.

1. QueryAirtableTable
2. StandardAsanaClientProviderService
3. ClientSideEncryptionSupport
4. AzureStorageUtils
5. StandardKustoIngestService
6. AbstractAzureLogAnalyticsReportingTask
7. DecryptContent
8. DecryptContentAge
9. DecryptContentCompatibility
10. EncryptContentAge
11. VerifyContentMAC
12. StandardDropboxCredentialService
13. AbstractEmailProcessor
14. GhostFlowRegistryClient
15. GhostControllerService
16. GhostFlowAnalysisRule
17. GhostParameterProvider
18. GhostProcessor
19. GhostReportingTask
20. Neo4JCypherClientService
21. GetHubSpot
22. AbstractIoTDB
23. StandardPGPPrivateKeyService
24. GetShopify
25. ListenSlack
26. ConsumeSlack
27. PublishSlack
28. SlackRecordSink
29. BasicProperties
30. V3SecurityProperties
31. ConsumeTwitter
32. OnePasswordParameterProvider
33. KerberosPasswordUserService
34. StandardOauth2AccessTokenProvider
35. GetWorkdayReport
36. ZendeskProperties