Set kernel version to 4.1.0-20260521-dbrbuild for DBR publish

add tag

Release custom tag to adopt new kernel exception

[KERNEL] Add geospatial type support to IcebergCompat V3 and WriterCo…

…mpat V3 (#6494)

#### Which Delta project/connector is this regarding?

- [ ] Spark
- [ ] Standalone
- [ ] Flink
- [x] Kernel
- [ ] Other (fill in here)

## Description

Add geospatial type support (`GeometryType`, `GeographyType`) to
IcebergCompat V3 and IcebergWriterCompat V3 validation in Delta Kernel.

The geospatial types and table feature were already added to the kernel
in #5885, #6321, #6425, and #6301, but were not wired into the
IcebergCompat checks. This causes tables with geometry/geography columns
to be rejected when icebergCompatV3 or icebergWriterCompatV3 is enabled.

## How was this patch tested?
Updated existing test suites.

## Does this PR introduce _any_ user-facing changes?
Tables with geometry or geography columns can now use icebergCompatV3
and icebergWriterCompatV3.

Set version to 4.0.1-20260410-dbrbuild for DBR kernel upgrade

Co-authored-by: Isaac

[Kernel] Geospatial stats parsing: handle geometry/geography as WKT s…

…trings (#6301)

<!--
Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://github.com/delta-io/delta/blob/master/CONTRIBUTING.md
2. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]
Your PR title ...'.
  3. Be sure to keep the PR description updated to reflect all changes.
  4. Please write your PR title to summarize what this PR proposes.
5. If possible, provide a concise example to reproduce the issue for a
faster review.
6. If applicable, include the corresponding issue number in the PR title
and link it in the body.
-->

#### Which Delta project/connector is this regarding?
<!--
Please add the component selected below to the beginning of the pull
request title
For example: [Spark] Title of my pull request
-->

- [ ] Spark
- [ ] Standalone
- [ ] Flink
- [X] Kernel
- [ ] Other (fill in here)

## Description

<!--
- Describe what this PR changes.
- Describe why we need the change.
 
If this PR resolves an issue be sure to include "Resolves #XXX" to
correctly link and close the issue upon merge.
-->

This is **PR 1 of 3** for geospatial data skipping support. It teaches
the stats system (JSON parsing, schema validation, DataFileStatistics)
to handle geometry/geography columns as WKT string values, and adds
GeometryUtils for WKT POINT parsing/formatting.

Delta spec: #4726

### Changes
- **StatsSchemaHelper**: Mark `GeometryType`/`GeographyType` as eligible
for min/max stats
- **JsonUtils**: Handle geometry/geography as WKT string in
`parseJsonValueToLiteral()`
- **SchemaUtils**: Add geometry/geography to supported types in
`validateSupportedType()`
- **DataFileStatistics**: Validate geometry/geography stats accept
string literals
- **DefaultJsonRow**: Decode geometry/geography JSON values as strings
- **GeometryUtils** (new): WKT POINT parsing (`parsePointXY`) and
formatting (`formatPointWKT`)

### PR dependency graph
```
master
  |
  +-- PR A (this): Stats Parsing + GeometryUtils
  |     |
  |     +-- PR B: Expressions + Predicate Translation
  |     |
  |     +-- PR C: Parquet / Data Layer
```

## How was this patch tested?

- `GeometryUtilsSuite`: 15 tests covering WKT parsing/formatting,
round-trips, error cases
- `DefaultJsonHandlerSuite`: pending test placeholder for
geometry/geography parsing

## Does this PR introduce _any_ user-facing changes?

Adds new table feature

---------

Co-authored-by: Uros Bojanic <uros.bojanic@databricks.com>

Improve test quality after self-review

- Restore the unconditional baseRowId/defaultRowCommitVersion assertions
  in checkActionsWrittenInJson for both V1 and V3. The previous change
  weakened coverage by skipping the V3 assertion, but the E2E tests
  always pass empty values so the assertion should remain.
- Extract commitSingleAction helper to reduce boilerplate and avoid
  scoping issues with scalafmt.
- Simplify regression test assertions (remove redundant message strings).

[Flink] Add KernelTable implementation (#5949)

<!--
Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://github.com/delta-io/delta/blob/master/CONTRIBUTING.md
2. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]
Your PR title ...'.
  3. Be sure to keep the PR description updated to reflect all changes.
  4. Please write your PR title to summarize what this PR proposes.
5. If possible, provide a concise example to reproduce the issue for a
faster review.
6. If applicable, include the corresponding issue number in the PR title
and link it in the body.
-->

#### Which Delta project/connector is this regarding?
<!--
Please add the component selected below to the beginning of the pull
request title
For example: [Spark] Title of my pull request
-->

- [ ] Spark
- [ ] Standalone
- [x] Flink
- [ ] Kernel
- [ ] Other (fill in here)

## Description
This PR add an base implementation of DeltaTable using Kernel.
<!--
- Describe what this PR changes.
- Describe why we need the change.
 
If this PR resolves an issue be sure to include "Resolves #XXX" to
correctly link and close the issue upon merge.
-->

## How was this patch tested?
Unit Tests
<!--
If tests were added, say they were added here. Please make sure to test
the changes thoroughly including negative and positive cases if
possible.
If the changes were tested in any way other than unit tests, please
clarify how you tested step by step (ideally copy and paste-able, so
that other reviewers can test and check, and descendants can verify in
the future).
If the changes were not tested, please explain why.
-->

## Does this PR introduce _any_ user-facing changes?
No
<!--
If yes, please clarify the previous behavior and the change this PR
proposes - provide the console output, description and/or an example to
show the behavior difference if possible.
If possible, please also clarify if this is a user-facing change
compared to the released Delta Lake versions or within the unreleased
branches such as master.
If no, write 'No'.
-->