[Feature] Adding simple mechanism for updating or appending rows at the Worksheet level in O365

[luissantosHCIT]

After ruminating through the Microsoft API, it is crazy Microsoft lacks an API endpoint outside the Table mechanism.
https://learn.microsoft.com/en-us/graph/api/resources/workbookworksheet?view=graph-rest-1.0

Other people have asked about it on Microsoft forums.
https://learn.microsoft.com/en-us/answers/questions/811341/is-there-any-graph-api-to-append-row-to-excel-work

Like seriously?!?!

Looking at their own sharepoint Excel implementation, they use an intermediary API instead of a direct one to broker these common operations:

1. Append rows.
2. Update rows.

So, I got frustrated and did some experimentation.
I am opening a PR next that has code to enable a few convenience methods to achieve these BASIC operations.
This nothing against O365. It's an amazing and pleasant codebase. Haha.
This is a long standing frustration with Microsoft implementations of... well... anything.
In this case, it's their REST API. I found Google's much simpler to work with by the fact they support free appending.

[alejcas]

yeah you are right!
Also the Excel O365 code could be improved a lot + there are a lot of missing features.
Anyway don't use to change a lot of cells as it is very slow.
I've reviewed your PR

[luissantosHCIT]

I might spend time to implement insert and delete row/columns in the future. So I might be back hopefully in the no so distant future with another PR. I need to take care of a few other responsibilities.

The method in the PR should be as efficient as it gets in my experimentation since the range update could be used for pushing a batch (I tested a 26x50 matrix of '???').

I don't think we need to overburden the project with every single Excel feature. If I come across a need I will make a patch for it and if no one has patched it (outside of you), then it is not a frequently used feature and I think you have captured 99% of that.

I think this project is excellent the way it is (as far as my excel usage is concerned) and all other pains are the fault of Microsoft. :P

[alejcas]

I started a review on your PR and I saw some errors? Can u please review my comments so I can accept the PR or you may have to change something

Thanks

[luissantosHCIT]

@alejcas Sorry, I do not see any comments on GitHub for #1180 and I do not see emails about it.
Would you be kind to share when able?
I will be happy to address your concerns and push a commit if appropriate.
Thank you!

[alejcas]

Don't you see the review?

[luissantosHCIT]

@alejcas I am not sure why, but your comments do not show in my PR.
I can see PR comments in other repos I contribute, but not in this one.

With that said, let me look into my mistake and correct it. This might be something I should add a test for in retrospect.

[luissantosHCIT]

@alejcas

You were right!

My initial attempt at generating column labels was garbage. I created a unit test and via the magic of TDD and thinking a bit more I came up with a simpler and more robust version that can hypothetically generate as long a label as the recursion stack limit allows. It should be a lot more than people probably typically use and maybe the API itself will break before my new function. Please review and I hope it makes up for my blunder.

I also cleaned up the documentation string.

Have an excellent day!