bip-0322: add another valid sig vector not to confuse

[ChrisCho-H]

Following this discussion, add another valid sig vector not to confuse developer.
It has been misleading some developers, as they think their implementation is wrong even if it's right.
This test vector is also included in ongoing implementation of BIP322(PR is closed but seems like still in development here)

[murchandamus]

Pinging @kallewoof

[kallewoof]

LGTM, atlhough it might be good if @luke-jr OK'd as well.

[murchandamus]

BIP champion approved this change, and it seems like an improvement to me. Any reservations on merging this, @luke-jr?

[luke-jr]

Sounds fine to me (though I didn't verify the crypto)

This test vector is also included in ongoing implementation of BIP322(PR is closed but seems like still in development here)

This was a branch I made for OCEAN to be compatible with BIP322 signatures. It isn't intended as further development of BIP322 nor support thereof for Core or Knots.

I did consider developing BIP322 further, but came to the conclusion I would need to break compatibility with the current draft, and unfortunately the current draft is already implemented.

IMO at this stage, it should be stripped down to the one case actually implemented (afaik just Simple) and marked Final (if someone wants to complete a new signature system that actually covers all the use cases correctly, it should be a new BIP).