Changing the structure of `atmos terraform ...`

## Describe the Feature

This is just my opinion, but the structure of `atmos` is a bit funky when compared to most other CLI tools.

I'm referring to this structure: `atmos terraform -s [options]`.

The `atmos` required arguments of component + stack being between command + options has thrown me and others off numerous times now.

## Expected Behavior

I'm hoping for a more intuitive structure.

## Use Case

N / A

## Describe Ideal Solution

My ideal structructure: `atmos terraform [options] -c -s `

## Alternatives Considered

N/A

## Additional Context

* If this is of interest to discuss further, I can shed more thoughts on this and try to find examples of new folks that I've introduced to atmos getting hung up on the current structure.

The issue names no files, tests, or entry points; first review the existing `atmos terraform` argument handling and the seven-comment discussion. Done means the command accepts the proposed component and stack option placement consistently, with the affected CLI behavior validated by appropriate tests.

Written by the indexing model from the issue text.