Remove ADLS hint from import

[N-o-Z]

Closes #7580

Change Description

Remove ADLS hint from import

Background

We are saving the physical address of imported objects in ADLS Gen2 accounts wrong which creates issues when using the physical address (to export tables for example)

Bug Fix

1. Problem detected when trying to export tables of data that was imported from and adls gen 2 account
2. On investigation we detected that the physical address is saved incorrectly for these type of accounts due to the hint (change in the url from blob to adls
3. The hint is not longer necessary due to improvements of the import mechanism, we can use only one adapter for it.
4. The quickest and best way to fix was to remove the hint and the old Azure BlobWalker

Testing Details

Verified by current unit and system tests

Breaking Change?

Yes - will require users who use the adls hint to stop using it

[github-actions]

♻️ PR Preview d9337ee has been successfully destroyed since this PR has been closed.

_{🤖 By surge-preview}

[github-actions]

E2E Test Results - DynamoDB Local - Local Block Adapter

[arielshaqed]

Worried about backwards compatibility: if someone has an old workflow or even script:

• We prefer not to break it
• We must give a useful error message if they try.

As is, we must document this change, and it seems like a major version bump.

As an alternative, we might translate the modified URLs back to their original form, and ideally issue a warning that we did so. (Other alternatives are possible, of course!)

[arielshaqed]

This breaks any existing import scripts. Does this mean we need a major release 🤢 ?

[N-o-Z]

As stated in the PR description - this is a breaking change. But I believe we can avoid a major release since this affects specific users we can identify

[N-o-Z]

Added a WA for lakectl so it doesn't break. Effectively this is only going to impact WebUI users (I'm fine with that)

[arielshaqed]

We should document the change. Otherwise someone who's already imported has no way of understanding what went wrong!

[N-o-Z]

Added deprecation message

[N-o-Z]

Worried about backwards compatibility: if someone has an old workflow or even script:

• We prefer not to break it
• We must give a useful error message if they try.

As is, we must document this change, and it seems like a major version bump.

As an alternative, we might translate the modified URLs back to their original form, and ideally issue a warning that we did so. (Other alternatives are possible, of course!)

We need to get rid of this - the sooner the better.
This "trick" was done for lack of any other viable alternative, and now that it's not required we should remove it. This already caused us bugs in the pre-signed url and delta export.
I think it's better to break it now while we have a handful of users who might use import in Azure ADLS Gen2, this way we can probably avoid releasing a major lakeFS version.

[N-o-Z]

@arielshaqed Added also backwards compatibility for the delta exporter

[arielshaqed]

Thanks!

[arielshaqed]

I prefer to say what is happening, not only what isn't:

Suggested change

	Warning("'adls' hint will be deprecated soon, please use the original source url for import")
	source = strings.Replace(source, "adls.core.windows.net", "blob.core.windows.net", 1)
	Warning("'adls' hint will be deprecated soon, please use the original source url for import")
	translatedSource = strings.Replace(source, "adls.core.windows.net", "blob.core.windows.net", 1)
	if source != translatedSource {
	Fmt(" Using %s\n", translatedSource)
	}