Replaced print in production with developer log

[adityathakurxd]

Description

Removes avoid_print: ignore from analysis_options.yaml and replaces all print() in production with developer.log()

Related Issues

I would suggest switching from print to dart:developer as it is suggested here https://flutter.dev/docs/testing/code-debugging#logging
Or there is a specific reason to stick with print?

Originally posted in #519 (comment)

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[miquelbeltran]

Hi @adityathakurxd and @vbuberen because we have two PRs solving the same issue, we cannot merge the two of them. This one landed first so I will go with this one, but I will add the hacktoberfest labels to both (if that was your goal).