chore: remove cargo-near-build as separate import in [dev-dependencies] (examples)

[virajbhartiya]

Closes #1257

Removed the individual export for cargo-near-build to use the default exported dependency

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.20%. Comparing base (d7c16c8) to head (d386133).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1263      +/-   ##
==========================================
- Coverage   80.23%   80.20%   -0.03%     
==========================================
  Files         102      102              
  Lines       14598    14598              
==========================================
- Hits        11712    11708       -4     
- Misses       2886     2890       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[virajbhartiya]

@dj8yfo can you please suggest me a way to include build_script in the imports

[dj8yfo]

@virajbhartiya please revert the change for build-script. This must be lines for factory-contract.
Importing it directly for build-scripts with additional features is ok, and is somewhat distinct purpose than routinely compiling contracts for tests.
Also these weren't referenced in the issue

[dj8yfo]

@virajbhartiya together with reverting examples/factory-contract you
removed lines with import use near_workspaces::cargo_near_build;
in tests of examples/fungible-token, examples/lockable-fungible-token, examples/non-fungible-token, did you?
Add these lines, and 6 test jobs should start passing

[dj8yfo]

@race-of-sloths score 2

[race-of-sloths]

@dj8yfo Thank you for calling!

@virajbhartiya Thank you for the contribution! Join Race of Sloths by simply mentioning me in your comment/PRs description and start collecting Sloth Points through contributions to open source projects.

What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow

For contributors:

• Tag @race-of-sloths inside your pull requests
• Wait for the maintainer to review and score your pull request
• Check out your position in the Leaderboard
• Keep weekly and monthly streaks to reach higher positions
• Boast your contributions with a dynamic picture of your Profile

For maintainers:

• Score pull requests that participate in the Race of Sloths and receive a reward
• Engage contributors with fair scoring and fast responses so they keep their streaks
• Promote the Race to the point where the Race starts promoting you
• Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

• For contributors
  • Include a PR: @race-of-sloths include to enter the Race with your PR
• For maintainers:
  • Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
  • Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
  • Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
  • Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called