## Summary
Fail smoke tests eagerly if one command fails.

## Background
Smoke test scripts kept executing even though some of their commands
failed. This patch uses the bash built-in `set -e` to immediately exit
tests with non-zero exit code.

## Changes
- Use `set -e` in all smoke tests.

## Testing
This correctly fails tests if the conditions don't apply (tested offline
and verified in CI).

## Related Issues
Partially addresses #1392.
This patch will fail CI until after
#1393 is merged.

## Summary
Fixes the conditionals that determine whether a smoke test passes.

## Background
Many smoke tests incremented a fetch-counter as long as it was `counter
< max`, but the test was for `counter > max`, which was never reached,
and hence the test passed succesfully even though it actually failed.
This was easily overlooked because so far the tests make use of the
posix-compatible `[ $counter -lt $max_counter ]` and `[ $counter -gt
$max_counter]`. But since all tests require bash this patch changes it
to use `(( ))`.

## Changes
- Change all smoke test scripts to use the the bashism `(( $counter <
$max_counter ))` for incrementing the counter, and `(( $counter >=
$max_counter ))` to check for failure.

## Testing
This correctly fails tests if the conditions don't apply (tested offline
and verified in CI).

## Related Issues
Partially addresses #1392.
This patch will fail CI until after
#1393 is merged.

* main:
  fix(test): use correct conditions to dermine smoke test success (#1395)
  fix(test): fail smoke test scripts eagerly if a command fails (#1394)
  fix(cli, tests): add force flag to overwrite withdrawal target path (#1393)
  release(charts): update with biweekly image cuts (#1399)
  Chore(Charts): seq-faucet bech32m chart update (#1301)
  chore: preview environment with astria-geth changes (#1401)
  release: biweekly release cut (#1398)

## Summary
Fail smoke tests eagerly if one command fails.

## Background
Smoke test scripts kept executing even though some of their commands
failed. This patch uses the bash built-in `set -e` to immediately exit
tests with non-zero exit code.

## Changes
- Use `set -e` in all smoke tests.

## Testing
This correctly fails tests if the conditions don't apply (tested offline
and verified in CI).

## Related Issues
Partially addresses astriaorg/astria#1392.
This patch will fail CI until after
astriaorg/astria#1393 is merged.

## Summary
Fixes the conditionals that determine whether a smoke test passes.

## Background
Many smoke tests incremented a fetch-counter as long as it was `counter
< max`, but the test was for `counter > max`, which was never reached,
and hence the test passed succesfully even though it actually failed.
This was easily overlooked because so far the tests make use of the
posix-compatible `[ $counter -lt $max_counter ]` and `[ $counter -gt
$max_counter]`. But since all tests require bash this patch changes it
to use `(( ))`.

## Changes
- Change all smoke test scripts to use the the bashism `(( $counter <
$max_counter ))` for incrementing the counter, and `(( $counter >=
$max_counter ))` to check for failure.

## Testing
This correctly fails tests if the conditions don't apply (tested offline
and verified in CI).

## Related Issues
Partially addresses astriaorg/astria#1392.
This patch will fail CI until after
astriaorg/astria#1393 is merged.