Xrpl-py

Added
- Support for the DID amendment (XLS-40).
- Support for `server_definitions` RPC

Fixed
- Exported `get_nftoken_id` and `parse_nftoken_id` at the `xrpl.utils` level
- Fixed issue in `get_nftoken_id` where error is opaque when there are no `NFTokenPage`s

Changed
- Removed sidechain-net1 Devnet faucet support as it has been decommissioned. Users should instead use the bridge between Devnet and sidechain-net2 for testing.
- Removed amm-devnet faucet support as is will soon be decommissioned

Added
- Added new syntax for `SetFee` pseudo transaction sent after the [XRPFees](https://xrpl.org/known-amendments.html#xrpfees) amendment. (Backwards compatible)
- Support for [XLS-38d (XChainBridge)](https://github.com/XRPLF/XRPL-Standards/tree/master/XLS-38d-XChainBridge)

Fixed
- Update request models related to AMM
- Better error handling for when a `Wallet` is passed into an account or destination field
- Fixed AMMBid fields (BidMin, BidMax) with correct type IssuedCurrencyAmount

Added
- Add AMM support [XLS-30](https://github.com/XRPLF/XRPL-Standards/discussions/78)

Added
- Added new `Clawback` transaction as per [XLS-39](https://github.com/XRPLF/XRPL-Standards/discussions/94)

Fixed
- Replaced alias for `classic_address` with separate property to work around this mypy issue:
https://github.com/python/mypy/issues/6700

Additions

Additions are intended to be non-breaking (because they are purely additive).

- `server_definitions`: A new RPC that generates a `definitions.json`-like output that can be used in XRPL libraries.
- In `Payment` transactions, `DeliverMax` has been added. This is a replacement for the `Amount` field, which should be no longer used - instead, use `delivered_amount` in transaction metadata. To ease the transition, `DeliverMax` is present regardless of API version, since adding a field is non-breaking. The field `Amount` is no longer present in `Payment`s in API version 2.