TakeOfferAndSubscribe should fail if provided amount is out of range
Here's what happens now. You have to look at the logs to figure out why the swap failed if the taker's provided amount is out of range. Alice's initial `TakeOfferAndSubscribe` should have returned an error, so the end user can get a good error message printed immediately by `swapcli`.

### Bob
```
$ ./bin/swapcli make --min-amount 0.1 --max-amount 0.1 --exchange-rate 0.1 --use-relayer
Published:
	Offer ID:  0x2c36492bdd46fa970dcb388325a09cb9e0a6d5e7b5b32411e9aa0f7e729bb3a2
	Peer ID:   12D3KooWNseb7Ei8Xx1aBKjSFoZ9PGfdxN9MwQxfSRxsBAyA8op4
	Taker Min: 0.01 ETH
	Taker Max: 0.01 ETH
```

### Alice
```
./bin/swapcli take --peer-id 12D3KooWNseb7Ei8Xx1aBKjSFoZ9PGfdxN9MwQxfSRxsBAyA8op4 \
  --offer-id 0x2c36492bdd46fa970dcb388325a09cb9e0a6d5e7b5b32411e9aa0f7e729bb3a2 \
  --provides-amount 0.1 \
  --swapd-port 5001
Initiated swap with offer ID 0x2c36492bdd46fa970dcb388325a09cb9e0a6d5e7b5b32411e9aa0f7e729bb3a2
2023-03-19-11:13:01 > Stage updated: ExpectingKeys
2023-03-19-11:13:01 > Stage updated: Aborted
```

Logs:
```
DEBUG	net	net/initiate.go:87	received message from peer, peer=12D3KooWGBw6ScWiL6k3pKNT2LR9o6MVh5CtYj1X8E1rdKu
eYLjv type=SendKeysMessage
INFO	xmrmaker	xmrmaker/net.go:104	**incoming take of offer 0x2c36492bdd46fa970dcb388325a09cb9e0a6d5e7b5b32
411e9aa0f7e729bb3a2 with provided amount 0.1**
WARN	net	net/initiate.go:104	failed to handle protocol message: err=1 ETH provided by taker is over offer max
imum of 0.1 XMR
```