Auto load .env file in current directory

[kkHAIKE]

And add short flag "-c" alias to "--collection"

[kkHAIKE]

I don't think it's necessary to add the --no-auto-env parameter.
The .env file is automatically loaded in many scenarios or tools. Even if a .env file not specifically written for the posting tool is loaded, the posting tool won't be affected (since it doesn't reference any variables from it).

The current best practice for using the posting tool is to prepare a directory with the following structure:

. 
|- collection_name 
\- .env

Normally, we cd into this directory and execute --collection name --env .env, which feels a bit redundant.
So in this commit, I've changed it to just require -c name.

If customizability is really desired, we could add config.yaml configuration options to achieve this.
or simply autoload posting.env instead of .env.

PS: Also, I wonder if having a global configuration for collections would be better? (Since the current posting approach suggests that collections shouldn't contain metadata).
I'm currently facing an issue where I need to repeatedly configure the same auth and script settings across all paths.

[darrenburns]

I think you're right regarding the no-auto-env param, I didn't think it through. I'll remove that.

edit: moved chat about global config to a discussion: #146 (comment)

[kkHAIKE]

Would it be better to autoload posting.env instead? This would avoid conflicts with other tools sharing the same .env file, while also being more explicit (not a hidden file) and clearly indicating its intended use.

[darrenburns]

Hmm - yes, that's a good point. I think it's better to be explicit about that since .env files inside are likely unrelated to Posting.