Make 'up' and 'up-bds' Makefile targets idempotent

[Endogen]

Problem

Running make up multiple times creates duplicate pm2 processes because the -f (force) flag always starts new processes even when ones with the same name already exist.

This leads to:

• Database lock errors: failed to create node: failed to initialize database: resource temporarily unavailable
• Resource waste: Multiple xian/cometbft processes running simultaneously
• Confusing pm2 output: Processes with the same name but different IDs

Example of the issue:

│ id │ name     │ status  │
├────┼──────────┼─────────┤
│ 1  │ xian     │ online  │
│ 2  │ cometbft │ online  │
│ 3  │ xian     │ online  │  ← duplicate
│ 4  │ cometbft │ errored │  ← duplicate, failed due to db lock

Solution

Delete existing processes before starting new ones:

up:
	@pm2 delete xian 2>/dev/null || true
	@pm2 delete cometbft 2>/dev/null || true
	cd ./src/xian && pm2 start xian_abci.py --name xian
	pm2 start "../cometbft node --rpc.laddr tcp://0.0.0.0:26657" --name cometbft

• The || true ensures no error on first run when processes don't exist yet
• Removed -f flag since we're now ensuring a clean state
• Same fix applied to up-bds target

Testing

Tested locally - running make up multiple times no longer creates duplicates.