[Feature] WIP: Allow to skip calling Read after Create/Update operations

[alexott]

Changes

This PR adds the ability for a resource to specify that it may not need to call Read after Create and Update operations so we can avoid performing another API call(s). The resource may implement CanSkipReadAfterCreateAndUpdate function that can decide if the Read operation should be skipped.

It was found that the import API returns object_id as a result of its execution, so we don't really need to call get-status to fill all attributes. This should help when we import a large number of notebooks, i.e., when applying exported resources.

TODOs:

• add unit test for a test resource that implements skipping
• check if we need to have a suppress diff for the language attribute
• add integration tests for DBC/Jupyter create and update

Tests

• make test run locally
• relevant change in docs/ folder
• covered with integration tests in internal/acceptance
• relevant acceptance tests are passing
• using Go SDK

[mgyucht]

Instead of adding this to the databricks_notebook schema, can we add it to common.Resource when defining the resource? Basically, we can change the create method to:

		resource.CreateContext = func(ctx context.Context, d *schema.ResourceData, m any) diag.Diagnostics {
			c := m.(*DatabricksClient)
			err := recoverable(r.Create)(ctx, d, c)
			if err != nil {
				err = nicerError(ctx, err, "create")
				return diag.FromErr(err)
			}
			if r.SkipReadAfterCreateAndUpdate {
				return nil
			}
			if err = recoverable(r.Read)(ctx, d, c); err != nil {
				err = nicerError(ctx, err, "read")
				return diag.FromErr(err)
			}
			return nil
		}

and same for update.

[alexott]

let me look

[eng-dev-ecosystem-bot]

Test Details: go/deco-tests/11598800362