`@looker/sdk-rtl` was encoding object values like

```ts
{ created_date: 'this year to second' }
```

as 
```ts
[object Object]
```

and now the value is JSON stringified instead

Updated the runtime information on Look#, Looker's C# SDK for .NET

feat: Revert "Update release-please version, add r-p config for Go, add Go publish CI (#1030)" (#1035)

Issue tracking the reason we can't update from v2 to v3 release-please. googleapis/release-please#1348

This reverts commit e597978f.

- Updated release-please to latest v3 from v2 that contains the needed functionality for releasing Go SDK. The breaking changes should not affect us: https://github.com/google-github-actions/release-please-action/releases/tag/v3.0.0
- Setup release-please config to release Go SDK at v0 only.-- To release Go SDK at v1 and above requires automated editing of  the module name in go.mod during SDK generation or when release-please creates a release PR. Release-please gi
thub issue: https://github.com/googleapis/release-please/issues/1344
-- The repo tag must be in the exact format of "go/vX.X.X". So package-name and tag-separator in release-please-config.json are set accordingly
- Setup release-please-manifest to point go sdk to 0.0.1. 0.0.0 is automatically bumped to 1.0.0 ignoring the "pre-major" release-please configs.
- Setup a go publish github action that publishes go module to go proxy based off the new tag
- Updated go.mod and go.sum with go mod tidy which cleans up
dependencies

* fix: Go SDK parses response by result type

Currently go sdk model generation doesn't support union type for responses like
RunQuery. So we cannot parse according to Content Type Header. For now, parse
based off model type.

We need to update sdk model generation to use interface{}
for union types, and then use Content Type Header to parse response accordingly.
This will break downstream dependencies.

- Added additional integration tests around queries looks and
  dashboards.
- Parse response based of type defined in go sdk models, the result type
- Added unit tests
- Return error body in addition to error status code.

* Added git issue in comment

* Added png/svg integration tests and updated integration tests to passing with new 22.4

Changes:
- An id type was being used in a test for int64. All ids are now strings so a different Int64 spec property is used now
- Refreshed the spec shadow copy in APIX. Perhaps we can remove this now?
- Changed looker doc redirect link pattern to reflect the removal of redirects from `looker.com/docs/r` to the new `docs.looker.com/r`pattern

* fix: 22_4 API

* fix: Additional fixes in unit tests for Hackathon

* fix: python integration tests for string id types

* fix: attempt to fix integration test for typescript

* fix TS SDK tests for new string IDs

* update python config notes, reformat python SDK files

* format python/looker_sdk/sdk/api{31,40}/methods.py

Co-authored-by: John Kaster <kaster@google.com>
Co-authored-by: Joel Dodge <joeldodge@google.com>

Turns out bazel build files have weird `stat`s that break node fs interrogation and hence break declaration miner.

This ignores errors reported on directory checking for those offending paths so indexing completes successfully

Hope to find a cleaner solution in the future but because this is an internal tool rarely used I don't want to spend more time on it right now

Unit test tweak to support Looker 22.4 API type changes

* ci: change workflows to use reusable action for looker versions

* fix: change supported-versions@v0.0.1 to @main

  Using a particular version here is a mistake since
  this would need to change for every new looker release.
  Instead use @main so that the supported-versions
  action will always use the latest version.

Co-authored-by: Dr. Strangelove <drstrangelove@google.com>

Co-authored-by: Joel Dodge <joeldodge@google.com>

* build: reset version action

* add filtering on sdk-codegen-all tag

Co-authored-by: Joel Dodge <joeldodge@google.com>

fixes #944

the main fix here is switching from `cattr.register_structure_hook` to
`cattr.register_structure_hook_func`. I re-organized some of the code
in an effort to reproduce the issue in the test_serialize.py suite but
I could not reproduce there, only in integration tests.

Now that it's a function, we don't need a generated hook per type.

I further isolated the converter usage switching the serializing to use
each 31/40 dedicated converter.

I also switched to the newer GenConverter.

setup testing against python 3.10

* chore: set version number

* move release-as to top-level for multiple packages now

Co-authored-by: Joel Dodge <joeldodge@google.com>

* feat: generate code deprecation tags

* update specs to latest 22.2 build

* updated go gen deprecations

Co-authored-by: Joel Dodge <joeldodge@google.com>

Bumps [prismjs](https://github.com/PrismJS/prism) from 1.25.0 to 1.27.0.
- [Release notes](https://github.com/PrismJS/prism/releases)
- [Changelog](https://github.com/PrismJS/prism/blob/master/CHANGELOG.md)
- [Commits](https://github.com/PrismJS/prism/compare/v1.25.0...v1.27.0

)

---
updated-dependencies:
- dependency-name: prismjs
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

This PR adds an optional config_settings parameter to the python sdk init functions. It is up to the sdk user to provide a valid implementation of the ApiSettings class.

Co-authored-by: Dr. Strangelove <drstrangelove@google.com>

* chore(deps): Update ansi-html version as suggested by dependabot

* chore(deps): Dependabot suggests that ansi-html has a vulnerability, replace with forked version.

* chore(deps-dev): Bump node-fetch from 2.6.5 to 2.6.7 in /examples/access-token-server

* chore(deps-dev): Bump node-fetch from 2.6.1 to 2.6.7

* chore(deps): Bump follow-redirects from 1.14.7 to 1.14.8

* fix(deps): Upgrade Axios to 0.21.2 based on dependabot alert

* fix(deps): Upgrade node-forge to 1.0.0 based on dependabot alert

* fix(deps): Upgrade postcss to 8.2.13 based on dependabot alert

* fix(deps): Upgrade json-schema to 0.4.0 based on dependabot alert

* chore(deps): Updated dependencies using "resolutions" section in package.json

Co-authored-by: Joel Dodge <joeldodge@google.com>

* Create simple_schedule_plan.py

Many people have come on chat about creating schedules with the sdk and I just wanted to create a barebones example, so we can direct them to a public example.

* Update README.md

Updated readme to point at simple_schedule_plan example

* Update README.md

Update readme to link to new example of adding users to a group from a CSV.

* updated readme to point at script which updates prod branches touse main rather than master

Co-authored-by: Joel Dodge <joeldodge@google.com>
Co-authored-by: Dr. Strangelove <drstrangelove@google.com>

Co-authored-by: Eric Lyons <53839634+eric-lyons@users.noreply.github.com>
Co-authored-by: Joel Dodge <joeldodge@google.com>

setting next sdk-rtl version to 21.3.3 because package.json and all the
dependencies currently point to 21.3.2 but release-please missed it so
next time it runs it thinks it will be starting at 21.3.1 which is what
is recorded in the last release at f8867339

Co-authored-by: Joel Dodge <joeldodge@google.com>

and pin sdk-codegen to a minor bump (semver from conventional commits would put it at 22.0.0 but I don't think we want that)