Use FutureWarning instead of DeprecationWarning in project.py

[Onkar627]

Description

Fixes issues as described by @vyasr in Issue #687 as we tend to change the DeprecationWarning to FutureWarning instead.

Motivation and Context

The main motivation of this change is basically that warnings of the deprecated features are visible to the users as in current scenarios of Deprecated warnings python hides these by default.

Types of Changes

• Documentation update
• Bug fix
• New feature
• Breaking change¹

¹The change breaks (or has the potential to break) existing functionality.

Checklist:

• I am familiar with the Contributing Guidelines.
• I agree with the terms of the Contributor Agreement.
• My name is on the list of contributors.
• My code follows the code style guideline of this project.
• The changes introduced by this pull request are covered by existing or newly introduced tests.

If necessary:

• I have updated the API documentation as part of the package doc-strings.
• I have created a separate pull request to update the framework documentation on signac-docs and linked it here.
• I have updated the changelog and added all related issue and pull request numbers for future reference (if applicable). See example below.

[codecov]

Codecov Report

Merging #691 (f92adb4) into master (c291e1e) will increase coverage by 0.01%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #691      +/-   ##
==========================================
+ Coverage   78.53%   78.54%   +0.01%     
==========================================
  Files          65       65              
  Lines        7141     7141              
  Branches     1565     1565              
==========================================
+ Hits         5608     5609       +1     
  Misses       1228     1228              
+ Partials      305      304       -1     

Impacted Files	Coverage Δ
signac/contrib/project.py	85.03% <57.14%> (ø)
signac/__main__.py	71.89% <0.00%> (+0.11%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c291e1e...f92adb4. Read the comment docs.

[bdice]

Hi @Onkar627, thank you for the pull request! It looks like the changes in this PR are good. I have a few requests for this PR before merging:

1. An important part of the pull request process is to include descriptions of what was changed and why. Descriptions and references to related issues helps reviewers and PR authors communicate effectively. Would you be able to write some description/motivation information in the top section of the PR description? Please include a link to the issue Use FutureWarning to report deprecations #687. Look at past pull requests for examples of what kinds of information to write.
2. Please rename this PR to "Use FutureWarning instead of DeprecationWarning in project.py" so that the intention of the pull request is clear.
3. Look over the PR checklist and mark the appropriate boxes. For example, this PR would probably be considered a "New feature." Additionally, you need to read over and check the boxes below that to acknowledge that you have read the contributing guidelines, agree to the contributor agreement, have added yourself to the contributor list, etc.

[Onkar627]

I have updated the PR @bdice ,please have a look and just ping if any changes are required :)

[bdice]

@Onkar627 Thank you! If you would like, please consider adding yourself to the list of contributors.

I'll add a changelog entry, and then merge this PR after you add yourself to the contributor list (you may decline if you'd rather not add yourself).

We will use the same changelog entry for #692, and just add the number of that PR in the same line.

[Onkar627]

@Onkar627 Thank you! If you would like, please consider adding yourself to the list of contributors.

I'll add a changelog entry, and then merge this PR after you add yourself to the contributor list (you may decline if you'd rather not add yourself).

We will use the same changelog entry for #692, and just add the number of that PR in the same line.

Surely,I will love to add.