updated files to support new tuple representation

[MahtabNorouzi]

Updated the tuple structure across the codebase from { kind: 'app', opcode: 'Tup', args: [...] } to { kind: 'tuple', elements: [...] }. This refactor improves clarity and consistency in tuple handling and removes support for the previous Tup syntax. All affected files and references have been modified accordingly.

[bugarela]

We actually don't need this! The IR transformer itself should already guarantee that we visited/transformed all of the elements before reaching the tuple. This works as it is right now because namespacedName is idempotent (it can be applied more than once and the result will be the same as if it was applied once, that is, f(x) = f(f(x))), but it will also work as if we remove this, and we should 😄

Suggested change

	exitTuple(tup: QuintTup): QuintTup {
	// Process each element of the tuple
	const namespacedElements = tup.elements.map(element => {
	// If the element is a name, apply the namespace
	if (element.kind === 'name' && typeof element.name === 'string') {
	return {
	...element,
	name: namespacedName(this.namespace, element.name), // Apply the namespace
	}
	}
	// Otherwise, return the element as-is
	return element
	})
	// Return a new tuple with namespaced elements
	return {
	...tup,
	elements: namespacedElements,
	}
	}

[bugarela]

As we did with the effects inferrer, I think we can also generalize something here so we don't have to repeat this code between exitTuple and exitApp. This will also repeat with the other structures (lists, maps, records, etc), so we can try to generalize when adding the next one.