Upgrade package connectivity_plus from 5.0.2 to 6.0.5

[palisadoes]

Rationale

1. This was previously attempted by the automated dependabot job but the PR tests failed.
2. This issue has been created to fix the issue as there may be multiple dependency requirements that need updating

This is a major revision upgrade and many files may need to be updated to the new syntax, functions, methods and classes

Task

1. Upgrade intl from 0.18.1 to 0.19.0.
2. Remove this package if it is:
   1. unused
   2. unnecessary. For example:
      1. the functionality can be maintained by using another package we are already using,
      2. If we are using only one function or class in the package you can consider replacing it with code that resides in this repository
      3. It is used by a feature that the end user is unlikely to ever use

Background Failing PRs

• Bump connectivity_plus from 5.0.2 to 6.0.5 #2545
• https://github.com/PalisadoesFoundation/talawa/actions/runs/10660171498/job/29543779036?pr=2545

Screenshot

The failing PR test has this output

Release Note Details

Bumps connectivity_plus from 5.0.2 to 6.0.5.

Commits

• e61b472 chore(release): prepare for release (#3165)
• 277f8b6 docs(connectivity_plus): Update plugin requirements in README (#3160)
• 312cb59 chore(release): prepare for release (#3111)
• a620cec chore(deps): bump web from 0.5.1 to 1.0.0 in /packages/connectivity_plus/conn...
• c1c0698 chore(all): Add pub.dev topics (#3097)
• 6661365 fix(all): changed homepage url in pubspec.yaml (#3099)
• 35a96b9 chore(deps): bump androidx.test.espresso:espresso-core from 3.5.1 to 3.6.1 in...
• 62cf414 chore(deps): bump androidx.test:runner from 1.5.2 to 1.6.1 in /packages/conne...
• ecc5714 refactor(all): Remove website files, configs, mentions (#3018)
• 1985272 chore(connectivity_plus): flutter_lints to ^4.0.0 (#2969)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[karthik14344]

@palisadoes I would Like to work on this issue.

[karthik14344]

@palisadoes I Upgraded package connectivity_plus from 5.0.2 to 6.0.5.. and removed the deprecated usages in the code and raised PR. Please review it.

[palisadoes]

@karthik14344 I have to unassign this to give someone else a chance. You have raised 3 PRs without successfully completing the task.

[sushilpandeyy]

@palisadoes please assign me this issue!

[palisadoes]

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.