feat: replaced aura fork with sp-partner-chains-consensus

[Klapeyron]

Overview

🗹 TODO before merging

• Ready

📌 Submission Checklist

• All commits are signed off (git commit -s) for the DCO
• Changes are backward-compatible (or flagged if breaking)
• Pull request description explains why the change is needed
• Self-reviewed the diff
• I have included a change file, or skipped for this reason:
• If the changes introduce a new feature, I have bumped the node minor version
• Update documentation (if relevant)
• Updated AGENTS.md if build commands, architecture, or workflows changed
• No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

• Additional tests are provided (if possible)

🔱 Fork Strategy

• Node Runtime Update
• Node Client Update
• Other:
• N/A

Links

[LGLO]

Can't be Apache, because it depends on "sc-consensus"

[Klapeyron]

I am not sure that is correct. We are not making any modifications to the GPL3 code here, also existing primitives we migrated from PC are Apache licensed and GPL3 with Classpath exception exists precisely to let you link/combine that code with software under other licenses — including Apache — without the combined work becoming GPL, so an Apache crate depending on sc-consensus is exactly the intended use

[LGLO]

Classpath exception gives you ability to use GPL3 for building binary without having to GPL3 the code that builds this binary.

This is clearly library crate, it has to be tainted with GPL3. Exception doesn't work here.