Project from token

[dfguerrerom]

To make this package more useful not only for ee service accounts, I have added the following:

• EARTHENGINE_TOKEN secrets, and make the authentication process optional when there is one or the other
• When a local user authenticates using earthengine authenticate, there is a way to set a project, you can do it by using eartheingine set_project "project_name", and the value will be stored in the credentials file, I have modified the initialization method so it can get the project from there.
• I've created a new test when there's a initialization from token

I hope I have gotten your idea with this.

[dfguerrerom]

@12rambau, I think there's something that doesn't allow to run the workflow jobs

[12rambau]

that's normal you are a first time contributor on this one. Let authorize it

[12rambau]

I'll take time to review it on sunday but as it is i think i won't let it fly. The reason why I force users to set the EARTHENGINE_PROJECT variable even when normal credentials are used is that i cannot rely on credentials to access the cloud project name consistently. So if any downstream code needs this variable then your test will only work with personnal token. I reported it in the Google issue tracker and I think it's a major flow of the project implementation: https://issuetracker.google.com/issues/325020447

[dfguerrerom]

@12rambau, I understand the issue, but what if we set the PROJECT variable as the first option, if the var is not there, we can opt to extract the project_id from the credentials file... if it is set, it will be used for both auths.