MAINT BREAK: Adding Attack Technique Abstraction

[rlundeen2]

Modifying the AttackTechnique abstraction, which contains a SeedTechniqueGroup and an attack, encapsulates the entire piece of an attack that we'll measure success with.

This PR

• Adds an identifier to the AttackTechnique class, which is Identifiable
• Adds the identifier to the AtomicAttackResultIdentity in AttackResult
• Adds AttackTechnique as the way to call AtomicAttacks
• Seed merging is added so techniques can be combined into an AttackSeedGroup
• Scenarios are updated to use this as a pattern when creating AtomicAttacks

After this, we'll include an AttackTechniqueRegistry which can query attacks in a reusable way, and scenarios can use the shared registry for attack strategies.

Breaking:

It breaks some memory queries, but only from very recent PRs

[hannahwestra25]

So i obviously missed the addition of the seed technique group. I think this interface makes sense but I'm concerned / getting confused between all of our Seed* classes (so approving since that's not the focus of this particular PR). Can you update this: https://microsoft.github.io/PyRIT/code/memory/memory-data-types/#messagepiece and maybe this one https://microsoft.github.io/PyRIT/code/memory/seed-database/ (with identifier info) ?