Issue #945: Adjust text of the edge AZAddSecret to consider App Instance Property Lock

[zh54321]

Description

Adjust text of the edge AZAddSecret to consider App Instance Property Lock

Motivation and Context

This PR partially addresses: Issue #945

Since March 2024 all new App registrations have the app instance property lock enabled by default.
This will lead to more and more false positives with the edge AZAddSecret, since it is not possible anymore to add secrets to the Enterprise Application.

This small text adjustment should warn BloodHound users that it is only possible to add new Secrets to an Enterprise Application if it is not protected by the App Instance Property Lock configuration in the corresponding App Registration.

How Has This Been Tested?

Ran locally

Types of changes

• Chore (a change that does not modify the application functionality)
• Text adjustment

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Bug: Azurehound / Bloodhound CE: "App Instance Property Lock" are not considered leading to wrong edges AZAddSecret #945
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

ZH54321 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}