docs(adr): add current consensus on bdd (#12909)

## Description



---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [ ] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [ ] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [ ] reviewed "Files changed" and left comments if necessary
- [ ] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)

docs/architecture/adr-059-test-scopes.md

@@ -243,7 +243,11 @@ It may be useful if test suites could be run in integration mode (with mocked te
 with e2e fixtures (with real tendermint and many nodes). Integration fixtures could be used
 for quicker runs, e2e fixures could be used for more battle hardening.
 
-A PoC is in progress for `x/gov` unit tests demonstrating BDD, helping to determine if
-BDD feature tests are recommended when building up illustrative and journey scenarios.
+A PoC `x/gov` was completed in PR [#12847](https://github.com/cosmos/cosmos-sdk/pull/12847) 
+is in progress for unit tests demonstrating BDD.
+Observing that a strength of BDD specifications is their readability, and a con is the
+cognitive load while writing and maintaining, current consensus is to reserve BDD use
+for places in the SDK where complex rules and module interactions are demonstrated.
+More straightforward or low level test cases will continue to rely on go table tests.
 
 Levels are network mocking in integration and e2e tests are still being worked on and formalized.