chore: remove terraform modules due to migration to observability-stack repo

.gitignore

@@ -1,43 +1,2 @@
 **/dist/**
-
-# Terraform
-**/.terraform/*
-*.tfstate
-*.tfstate.*
-*.tfplan
-.terraform.lock.hcl
-crash.log
-.terraform/
-terraform.tfvars
-terraform.tfvars.json
-*.backup
-*.bak
-crash.log
-crash.*.log
-
-# Exclude all .tfvars files, which are likely to contain sensitive data, such as
-# password, private keys, and other secrets. These should not be part of version
-# control as they are data points which are potentially sensitive and subject
-# to change depending on the environment.
-*.tfvars
-*.tfvars.json
-
-# Ignore override files as they are usually used to override resources locally and so
-# are not checked in
-override.tf
-override.tf.json
-*_override.tf
-*_override.tf.json
-
-# Include override files you do wish to add to version control using negated pattern
-# !example_override.tf
-
-# Include tfplan files to ignore the plan output of command: terraform plan -out=tfplan
-# example: *tfplan*
-
-# Ignore CLI configuration files
-.terraformrc
-terraform.rc
-.terraform.lock.hcl
-
 venv

README.md

@@ -136,6 +136,10 @@ Issues are synced by the [gh-jira-sync-bot](https://github.com/canonical/gh-jira
 The bot configuration lives in [.github/.jira_sync_config.yaml](https://github.com/canonical/observability/blob/main/.github/.jira_sync_config.yaml); *carefully* read the README to configure it. This 
 takes care of most things, except the Jira labels, which are added by the *Jira automation*.
 
+## Terraform
+
+The COS product Terraform modules exist in [observability-stack/terraform](https://github.com/canonical/observability-stack/tree/main/terraform/), where you can find references to all the other Observability charm Terraform modules.
+
 ## Scripts
 
 This repository contains a `scripts` directory for helper scripts of various nature as `pip-installables`.