FR: Improve NoMAD.app Path With KeychainAdd
Description
KeychainAdd mech currently uses hard coded /Applications/NoMAD.app path when granting access in the generated keychain entry. If NoMAD is not installed to this hard coded path the keychain entry won't have the correct application permissions.
Proposal
I admit I might have a non-standard deployment since my NoMAD.app is installed to /Applications/Utilities. Still think one of these two options is better...
- Search for NoMAD in /Applications and subfolders to define the path
- Add a new preference key to set the search base or expected path to NoMAD