Migrate Storage Datalake to TypeSpec

# Goal

Update the Storage Datalake package to use TypeSpec instead of autorest

# Principles

- This is primarily an exercise to migrate the tool chain. This is NOT an exercise to
- Improve the convenience layer to latest guidelines
- Ask for new complex features in TypeSpec in order to remove already written manual convenience layer. For instance, paging in Storage couldn't be generated with autorest and was manually written. We don't plan to make TypeSpec support Storage paging out of the box, we'll just keep for now the convenience layer that exists. Easy TypeSpec update can be considered, as long as this doesn't impact the timeline in an unhealthy way.
- As this is an internal toolchain update, there should be no reason to update tests or re-record tests. It's actually a great regression testing to confirm that we're able to change the internal layers of Storage, without having to touch the test folder at all
- No breaking changes are allowed (APIView shouldn't even realize there was a change)

# Spec

We owned this branch, and should push all tspconfig and client.tsp updates directly there (no review needed yet):
https://github.com/Azure/azure-rest-api-specs/tree/feature/datalake-tsp/specification/storage/data-plane/DataLakeStorage

`tsplocation` should target this branch for now

# Reference

More details and update on the [loop paage](https://microsoft.sharepoint.com/:fl:/s/4b8cd56b-6d40-4ab3-bea5-1744d4d73cdf/IQCVtwVSrfJ3Q6ZDSlY42ayEAYd_nPaeWNWHG6x7S8PjnXs?e=gGUlYa&nav=cz0lMkZzaXRlcyUyRjRiOGNkNTZiLTZkNDAtNGFiMy1iZWE1LTE3NDRkNGQ3M2NkZiZkPWIlMjFvcWVpNUNkU2owU0JoMUJuLVFQTjJxSzBYVnBPaWFGUGhzZ1BUaEdSTnRvNDNjM1JLMU05UXA0T1ZxZlV3b2VpJmY9MDFVUVdFWVBNVlc0Q1ZGTFBTTzVCMk1RMktLWTROVExFRSZjPSUyRiZhPUxvb3BBcHAmcD0lNDBmbHVpZHglMkZsb29wLXBhZ2UtY29udGFpbmVy)