[ZEPPELIN-6676] Match notebook status, result codes and dataset types to server values

[miinhho]

What is this PR for?

The SDK declares paragraph status and result codes as open strings and omits SVG and NULL dataset types. Match these declarations to the server?s seven job states, four result codes and eight dataset types.

Update the affected consumers in the same PR. Use the server?s terminal-state classification, render SVG as an encoded image, and clear previous output for NULL. Prevent pending output work from restoring content cleared by SVG or NULL. Keep explicit handling for every dataset type without changing existing unsupported-type behavior.

Server evidence:

• zeppelin-interpreter/src/main/java/org/apache/zeppelin/scheduler/Job.java:56-80
• zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/InterpreterResult.java:40-61

What type of PR is it?

Bug Fix

Todos

• Correct finite types and adapt affected consumers.
• Add type, rendering and output-transition regression tests.

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-6676

Slice 1 of 3: finite value corrections. Structural/scalar corrections and Angular object removal compatibility will follow as separate PRs after this slice merges.

How should this be tested?

Run from the repository root after installing frontend dependencies:

cd zeppelin-web-angular
npm run typecheck:sdk-contracts
npm run test:shell
npm run check:websocket-contract
npx ngc -p src/tsconfig.json --noEmit

cd projects/zeppelin-react
npm test

Screenshots (if appropriate)

Not required.

Questions:

• Does the license files need to update? No.
• Is there breaking changes for older versions? TypeScript callers using arbitrary status/result strings must narrow them to the exported types. No server wire-format change.
• Does this needs documentation? The type migration note is included above.

[miinhho]

This branch has another change from other pr. I will close this pr and reopen with the changes I intended