fix(types): Add definition of returning in SaveOptions as it was missing.

[onozaty]

Pull Request Checklist

• Have you added new tests to prevent regressions?
• If a documentation update is necessary, have you opened a PR to [the documentation repository](https://github.com/sequelize/website/)?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Does the name of your PR follow our conventions?

Description Of Change

In the type definition file, the return of SaveOptions was omitted.

sequelize/src/model.d.ts

Lines 1284 to 1307 in cb8ea88

	/**
	* Options used for Instance.save method
	*/
	export interface SaveOptions<TAttributes = any> extends Logging, Transactionable, Silent, Hookable {
	/**
	* An optional array of strings, representing database columns. If fields is provided, only those columns
	* will be validated and saved.
	*/
	fields?: (keyof TAttributes)[];
	/**
	* If false, validations won't be run.
	*
	* @default true
	*/
	validate?: boolean;
	/**
	* A flag that defines if null values should be passed as values or not.
	*
	* @default false
	*/
	omitNull?: boolean;
	}

They are present in the actual code.

sequelize/src/model.js

Lines 4016 to 4022 in cb8ea88

	if (options.returning === undefined) {
	if (options.association) {
	options.returning = false;
	} else if (this.isNewRecord) {
	options.returning = true;
	}
	}

This pull request adds the missing returning.

There was no problem with the v7 codes.

Todos

[ephys]

Small code style change, but otherwise good to go

[ephys]

Thank you!

[github-actions]

🎉 This PR is included in version 6.37.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀