Make configure.py non-interactive
@crroush,
Could you please elaborate about your Feature and please specify the Use Cases for this feature. 

Also TensorFlow builds are **configured** by the .`bazelrc` file in the repository's root directory. The ./configure or `./configure.py` scripts can be used to adjust common settings.

https://www.tensorflow.org/install/source#configure_the_build

There is also a python version of this script, .**/configure.py**. If using a virtual environment, python `configure.py` prioritizes paths within the environment, whereas ./configure prioritizes paths outside the environment. In both cases you can change the default. Thank you!
 I was using the python script, but I cannot just pass the configuration into the python script, I have to interactively type them in, so I am unable to automate this process.  I have to build it for 3-4 architectures, so I would rather this process not require an engineer typing in commands.  

I am not that familiar with bazel, so if I can drop in different .bazelrc with my custom configs and forgo the  configure.py that will get me to the same goal.  
### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

r2.6
### Custom code

Yes

### OS platform and distribution

centos / redhat 7.x

### Mobile device

_No response_

### Python version

3.6

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Right now you have to manually select all of your options for building tensorflow from source.  When you are wanting to optimize across various architectures this becomes manually intensive.  It would be much better if you could pass the various arguments via the command line to setup your environment, instead of being forced to accept or override the default arguments.  


### Standalone code to reproduce the issue

```shell
run `./configure`
```


### Relevant log output

_No response_