atlasaction: report actions result via the Reports-API on Bitbucket

[giautm]

No description provided.

[github-actions]

Atlas Lint Report

Analyzed migrations

Status	Step	Result	Diagnostics
	Detect New Migration Files	Found 0 new migration files (from 0 total)
	Replay Migration Files	Loaded 0 changes on dev database
	Connect your project to Atlas Cloud to get more safety checks

---

Migrations automatically reviewed by Atlas

[github-actions]

Atlas Lint Report

Analyzed migrations2

Status	Step	Result	Diagnostics
	Detect New Migration Files	Found 0 new migration files (from 0 total)
	Replay Migration Files	Loaded 0 changes on dev database
	Connect your project to Atlas Cloud to get more safety checks

---

Migrations automatically reviewed by Atlas

[github-actions]

atlas migrate lint on atlasaction/testdata/migrations_destructive

Status	Step	Result
	1 new migration file detected	20230925192914.sql
	ERD and visual diff generated	View Visualization
	Analyze 20230925192914.sql 1 reports were found in analysis	Destructive changes detected Dropping table "t1" (DS102)
Read the full linting report on Atlas Cloud

[github-actions]

atlas migrate lint on migrations

Status	Step	Result
	No migration files detected
	ERD and visual diff generated	View Visualization
	No issues found	View Report
Read the full linting report on Atlas Cloud

[github-actions]

Atlas detected changes to the desired schema

Migration Plan (View on Atlas Cloud)

-- Create "t1" table
CREATE TABLE `t1` (
  `c1` integer NOT NULL
);
-- Create "t2" table
CREATE TABLE `t2` (
  `c1` integer NOT NULL
);
-- Create "t3" table
CREATE TABLE `t3` (
  `c1` integer NOT NULL,
  `c2` integer NOT NULL
);

Atlas lint results

Status	Step	Result
	Detect schema changes	3 new statements detected
	No issues found

---

📝 Steps to edit this migration plan

1. Run the following command to pull the generated plan to your local workstation:

atlas schema plan pull --url "atlas://atlas-action/plans/pr-272-R1cGcSfo" > pr-272-R1cGcSfo.plan.hcl

2. Open pr-272-R1cGcSfo in your editor and modify it as needed. Note that the result of the plan should align
the database with the desired state. Otherwise, Atlas will report a schema drift.

3. Push the updated plan to the registry using the following command:

atlas schema plan push --pending --file pr-272-R1cGcSfo.plan.hcl

4. Re-trigger the schema/plan action to update this comment:

gh run rerun 12412432170

[giautm]

We need better LogoURL